instinct
25Command
Manage instincts (confidence-based rules from session experience).
Command
Manage instincts (confidence-based rules from session experience).
Command
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.
Command
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).
Command
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.
Command
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.
Command
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.
Command
Analyzes and summarizes the agent monitor logs.
Command
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.
Command
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.
Command
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
Command
Develops the Business Model with Business Model Canvas, sharpens the value proposition, and defines a first pricing approach. The result is BUSINESSMODEL.md as the economic foundation of the project.
Command
Defines the feature scope of the project, prioritises using MoSCoW, and clearly defines the MVP scope. The result is FEATURES.md and MVP.md as the binding basis for architecture and planning.
Command
Creates a first financial plan with Cost Structure, Revenue Forecast, and break-even analysis. The goal is not exact bookkeeping but a plausible set of numbers that demonstrates the economic viability of the venture.
Command
Develops detailed personas, user journeys, and usage scenarios based on the Discovery results. These artefacts form the user foundation for all further conception decisions.
Command
Conducts a systematic initial assessment of data protection requirements: What personal data is processed, on what legal basis, and what DSGVO (GDPR) obligations arise from this? The result is a well-founded DSGVO initial assessment as a mandatory component of the Concept.
Command
Systematically lists all critical Assumptions from the conception phase and prioritises them by risk and validatability. The result is an Assumptions register that serves as the working basis for all further validation steps.
Command
Checks critical market, pricing, and demand Assumptions from the Assumptions register using concrete research, data, and competitive analyses. The result is confirmed or refuted Assumptions as the basis for informed Concept decisions.
Command
Builds a minimal technical Proof of Concept for the riskiest technical area of the project. The goal is not a finished feature but proof that the planned approach fundamentally works – before investing in architecture and implementation.
Command
Validates the regulatory Assumptions from Phase 1 concretely and practically: Is the venture legally implementable? Which hurdles are real, which are surmountable? The result is a robust regulatory validation as the Decision basis for Gate 2.
Command
Documents all significant architectural decisions as ADRs.
Command
Creates the system architecture overview with component diagram, responsibilities and data flows.
Command
Defines the non-functional requirements (scalability, performance, availability, maintainability).
Command
Selects the tech stack and justifies each technology decision.
Command
Designs the system architecture, selects the tech stack and documents architectural decisions. Each concern is its own sub-skill.
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: