{"id":4697,"external_id":"plugins_6aa30189c87c8191b7a17a88212d4d18","name":"engineering-suite-plan","display_name":"Plan","developer":"Saul Martí","category":"Developer Tools","listing_language":"en","listing_language_details":{"method":"cld-0.13.0/listing-v1","reliable":true,"detected_at":"2026-10-01T13:22:05Z","input_sha256":"3fe083b1ba1b75c5719533195d20dcc35f511201e0fca0b545c40f575f312770","source_fields":["release.description","release.interface.short_description","release.interface.long_description"]},"version":"2.0.0","skill_count":5,"first_seen_at":"2026-09-30T22:02:35.000Z","last_seen_at":"2026-10-03T06:00:00.871Z","last_changed_at":"2026-09-30T22:02:35.000Z","install_count":null,"search_matches":[],"research_summary":null,"research_reviewed_at":null,"metadata":{"canonical_app_id":null,"connector_id":null,"created_at":"2026-09-10T19:46:04.751899Z","discoverability":"UNLISTED","id":"plugins_6aa30189c87c8191b7a17a88212d4d18","is_template":false,"name":"engineering-suite-plan","release":{"app_ids":[],"app_manifest":null,"app_templates":[],"description":"Turn sufficiently understood requirements into technical plans, specifications, architecture decisions, and implementation breakdowns without implementing the work.","display_name":"Plan","id":"pluginrel_e05d8f7d9a708191a6eac3bb1f8d5236","interface":{"brand_color":"#22C55E","capabilities":["Turn requirements into plans"],"category":"Developer Tools","composer_icon_dark_url":null,"composer_icon_url":"https://files.openai.com/content?id=file_00000000009481f695a54cf1000e3275","default_prompt":"Turn these requirements into an implementation plan","default_prompts":["Turn these requirements into an implementation plan","Create a specification for this feature before coding","Stress-test this technical plan before we commit to it"],"developer_name":"Saul Martí","logo_url":"https://files.openai.com/content?id=file_000000003b5881f49a098a57a3c6730d","logo_url_dark":null,"long_description":"Turn sufficiently understood requirements into technical plans, specifications, architecture decisions, and implementation breakdowns without implementing the work.","plugin_category_id":"developer tools","privacy_policy_url":null,"screenshot_urls":[],"short_description":"Turn requirements into plans","terms_of_service_url":null,"website_url":null},"keywords":["engineering-suite","plan","skills"],"onboarding_skill_name":null,"requires_local_executor":false,"skills":[{"description":"Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.","interface":{"brand_color":null,"default_prompt":null,"display_name":"documentation-and-adrs","icon_large_url":null,"icon_small_url":null,"iconography":"pen","short_description":"Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase."},"name":"documentation-and-adrs","plugin_release_skill_id":"pluginrsk_6aa3018da1f08191b3ecdeeec6acd7c9"},{"description":"Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.","interface":{"brand_color":null,"default_prompt":null,"display_name":"doubt-driven-development","icon_large_url":null,"icon_small_url":null,"iconography":"radar","short_description":"Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later."},"name":"doubt-driven-development","plugin_release_skill_id":"pluginrsk_6aa3018ce0bc8191b70424e98592951f"},{"description":"Use whenever the Plan plugin is selected. Route the request to the intended bundled workflow while keeping all dependencies internal to this plugin.","interface":{"brand_color":null,"default_prompt":null,"display_name":"entry-plan","icon_large_url":null,"icon_small_url":null,"iconography":"hierarchy","short_description":"Use whenever the Plan plugin is selected. Route the request to the intended bundled workflow while keeping all dependencies internal to this plugin."},"name":"entry-plan","plugin_release_skill_id":"pluginrsk_6aa3018c771c8191a58ad42afd63741c"},{"description":"Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.","interface":{"brand_color":null,"default_prompt":null,"display_name":"planning-and-task-breakdown","icon_large_url":null,"icon_small_url":null,"iconography":"hierarchy","short_description":"Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible."},"name":"planning-and-task-breakdown","plugin_release_skill_id":"pluginrsk_6aa3018c784c8191995fdd80451bee4b"},{"description":"Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.","interface":{"brand_color":null,"default_prompt":null,"display_name":"spec-driven-development","icon_large_url":null,"icon_small_url":null,"iconography":"hierarchy","short_description":"Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying."},"name":"spec-driven-development","plugin_release_skill_id":"pluginrsk_6aa3018ccd0881919935aac67ab7a855"}],"version":"2.0.0"},"scope":"GLOBAL","status":"ENABLED"},"research":null,"package_metadata":{"name":"engineering-suite-plan","author":{"name":"Saul Martí"},"license":"MIT","sources":[{"path":".codex-plugin/plugin.json","sha256":"8190d4c02f8ebc952d4830aa098f99e80d36598449cf0cca1010686419c1f5bc"}],"version":"2.0.0","keywords":["engineering-suite","plan","skills"],"artifact_id":17236,"observed_at":"2026-10-03T06:34:58Z","capabilities":["Turn requirements into plans"],"field_sources":{"name":0,"author":0,"license":0,"version":0,"keywords":0,"capabilities":0},"extraction_version":1,"conflicts_or_errors":[]}}