This command analyzes an open decision question, automatically determines which perspectives are relevant, assembles the appropriate analysis agents, and develops a structured decision basis (Decision Basis) – without making the decision itself. That is the PO's responsibility.
This command creates one or more epics – either derived from an existing concept or roadmap, or standalone from a free description. An epic can already contain rough associated user stories or be created as a pure high-level shell – this is selectable per call.
Checks whether all criteria of the Discovery phase have been met and prepares the Go/No-Go Decision. No argument – this gate always checks the complete checklist.
Checks whether all results of the conception phase are complete and robust, and prepares the transition to the validation phase. No argument – this gate always checks the complete checklist.
Checks whether all critical Assumptions have been validated and a well-founded Go/No-Go/Pivot Decision can be made. This is the most important gate in the model – here it is decided whether to invest in the cost- and time-intensive architecture and implementation phase. No argument – this gate always checks the…
Checks whether all architecture and design decisions are completely documented and robust before transitioning into the planning and implementation phase. No argument – this gate always checks the complete checklist.
Checks whether all organizational and technical prerequisites are met to begin implementation. This is a readiness gate – all participants must know what to do first. No argument – this gate always checks the complete checklist.
Checks at the end of each sprint whether all tasks meet quality standards and the sprint can be considered successfully completed. Called repeatedly after each sprint. No argument – this gate always checks the complete current sprint status.
Invokes the project-guide agent as the entry point for the current project: structured status snapshot, prioritised next steps with command/agent recommendation, and disambiguation for unclear requests.
This command updates an existing rough concept based on new findings, clarified open questions, or changed requirements. Each revision is versioned and timestamped so that the evolution of the concept remains traceable.
This command guides through the initial conception phase as a Product Owner. The result is a first structured rough concept that serves as the basis for further steps (user stories, roadmap, stakeholder presentation).
Creates or revises docs/FRAME.md (Single-Source-of-Truth of the Lean-Track) and docs/CLAUDE-lean.md (slim project CLAUDE for Lean mode). Replaces the entire P0+P1+P3 conception work in the Lean-Track with a compact single-screen document.
Creates docs/LEARNINGS.md with hypothesis check, observations, and decision (PROMOTE / PIVOT-Soft / PIVOT-Hard / DROP). Closes a Lean cycle and determines what happens next.
Creates docs/PROMOTIONBRIEF.md as a structured bootstrap input for /project-init. Archives Lean artifacts (FRAME, LEARNINGS, CLAUDE-lean) to docs/lean-archive/. Code stays in the same repo; Full-Track decides per module: keep / refactor / rebuild.
Delivers a first market assessment: Is there demand? Who are the competitors? Is the idea roughly viable economically? The result is an overview needed for the Go/No-Go Decision at Gate 0.
Defines the core problem of a project or business idea and identifies the first rough Target Audience. The result is a clear problem statement that serves as the foundation for all subsequent phases.
★not rated 1
changed 1mo agoA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: