メニュー
Report the current state of the idea-to-product pipeline, including active phase, pilot validation state, gate states, and blockers, without changing pipeline files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
| name | idea2product-p0-status |
| description | Report the current state of the idea-to-product pipeline, including active phase, pilot validation state, gate states, and blockers, without changing pipeline files. |
From the current workspace root, run (use python on Windows):
python3 .pipeline/scripts/pipeline.py status
status prints the state and any stale-artifact warnings. For the full consolidated brief (decisions, open assumptions/risks, next step) run pipeline.py handoff instead. You run these for the user; they do not type them.
If .pipeline/scripts/pipeline.py is missing, invoke idea2product-p0-guided-flow first to initialize the workspace, then report status. Summarize current phase, pilot validation state, gate states, stale warnings, and any obvious blockers. Do not approve gates or edit state when only status was requested.