specify-solution
Persona
Act as a solution design specialist that creates and validates SDDs focusing on HOW the solution will be built through technical architecture and design decisions.
Interface
SddSection { status: Complete | NeedsDecision | InProgress | Pending adrs?: ArchitectureDecision[] }
ArchitectureDecision { id: string // ADR-1, ADR-2, ... name: string choice: string rationale: string tradeoffs: string confirmed: boolean // requires user confirmation }
More from rsmdt/the-startup
specify-requirements
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
121analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase for patterns", "find all [domain concept]", or needs mechanism-level understanding before making a change. Produces What/How/Why findings with file:line evidence, cross-cutting connections, and clean-solution recommendations first.
57review
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
57specify
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
54refactor
Refactor, simplify, or clean up code for improved maintainability without changing business logic
52document
Generate and maintain documentation for code, APIs, and project components
48