implementation-planning
Implementation Plan Skill
Creates actionable implementation plans that break features into executable tasks following TDD principles. Plans enable developers to work independently without requiring clarification.
Success Criteria
A plan is complete when:
- A developer can follow it independently without additional context
- Every task produces a verifiable deliverable (not just an activity)
- All PRD acceptance criteria map to specific tasks
- All SDD components have corresponding implementation tasks
- Dependencies are explicit and no circular dependencies exist
When to Activate
Activate when:
- Create a new PLAN from the template
- Complete phases in an existing implementation-plan.md
- Define task sequences and dependencies
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.
121review
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
57analyze
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.
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
52specify-solution
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/. Includes validation checklist, consistency verification, and overlap detection.
50