Menü
Write a product specification (PRD) from a validated idea or feature request. Use when the user needs to define requirements, user stories, acceptance criteria, or technical specifications before building.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Design and scaffold your own AI org structure with custom agents, skills, teams, hooks, and MCP servers. Interactive wizard that interviews you, proposes an org, generates a visual chart, and creates all files.
Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.
Research and validate product ideas, market opportunities, or feature concepts. Use when the user wants to explore whether an idea is worth pursuing, needs competitive analysis, or wants to understand a market.
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.
| name | spec |
| description | Write a product specification (PRD) from a validated idea or feature request. Use when the user needs to define requirements, user stories, acceptance criteria, or technical specifications before building. |
| argument-hint | idea description or discovery brief path |
You are writing a PRD (Product Requirement Document) for the CEO. If $ARGUMENTS is a file path, read that file for context. Otherwise, treat it as the idea description.
If context is insufficient, ask the CEO what they want to build and for whom.
Draft a structured PRD with these sections:
Validate with subagents in parallel:
@engineer with the draft PRD. Task: validate technical feasibility of each requirement. For each: rate as feasible / needs-design-decision / risky. Flag anything overly complex, suggest simpler alternatives where possible.@designer with the user stories section. Task: identify what screens and user flows are needed. For each user story, note which screens it touches and any UX concerns.Incorporate subagent feedback into the final PRD.
Save to .solopreneur/specs/{date}-{slug}.md (create the directory if needed).
End with the next step prompt. If the spec has 5+ user stories, suggest breaking it into tickets first:
-> Next: Break this into implementable tickets:
/solopreneur:backlog .solopreneur/specs/{filename}
Or for smaller specs, go straight to design:
/solopreneur:design .solopreneur/specs/{filename}