メニュー
Use when starting a new product from a raw idea, pressure-testing startup viability, or moving through blueprint, requirements, and system-design stages that produce durable reference docs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a request will produce frontend UI, a visual asset, an image prompt, or a video prompt, AND the intent/style is not already fully specified by the user or an existing design system in the repo. Forces a minimal, checkable design-context object to exist before generation so output does not default to generic/templated. Do NOT use for: single-property edits (color, spacing, copy tweak) with no ambiguity; bug fixes; refactors; or when the user already gave complete visual specs and you only need to execute. For those, just do the work.
Root orchestrator. Reads durable state, routes to one phase, dispatches fresh workers.
Pre-implementation alignment gate. Checks spec / plan / tasks consistency and plan vs codebase reality before code is written.
Define the goal: what problem we solve, for whom, and what success looks like. The directional anchor that architecture and specs must serve.
RED-GREEN-REFACTOR implementation per task. Each task passes before next. Produces handoff.md with reproducible evidence.
Design architecture: components, API schema, DB model, impact analysis, test strategy.
| name | greenfield-product |
| description | Use when starting a new product from a raw idea, pressure-testing startup viability, or moving through blueprint, requirements, and system-design stages that produce durable reference docs. |
This router owns the optional greenfield product family. It chooses exactly one child skill, hands off cleanly, and does not perform the child workflow inline.
Read child inventory for the authoritative stage order, per-child route conditions, prerequisites, and install hints.
Each child lives under greenfield-product/<child-name>/, and child SKILL.md files should say they are nested product-family children.
startup-pressure-test (raw idea, GTM realism, CAC/churn/runway, whether the thesis survives contact with the market)spec-pipeline (strategic blueprint → requirements → system design; three stages in one child)The spec-pipeline child consolidates three formerly separate stages (product-blueprint, requirements-writer, system-architect) into a single pipeline that produces .agents-stack/reference/design.md, .agents-stack/reference/product/requirements.md, and .agents-stack/reference/architecture/implementation.md.
If the request would skip a prerequisite stage, route to the prerequisite stage within the pipeline or to startup-pressure-test first.
.agents-stack/reference/design.md, .agents-stack/reference/product/requirements.md, and .agents-stack/reference/architecture/implementation.md exist, defined-feature delivery hands off to the implementation workflow under using-agents-stack.