Loading...
Loading...
Found 21 Skills
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Structured development workflows using /brainstorm, /write-plan, and /execute-plan patterns. Transform ad-hoc conversations into systematic project execution with hypothesis-driven planning, incremental implementation, and progress tracking.
Execute task planning based on the specified file and manage questions[/todo-task-planning file_path --pr --branch branch_name]
Use this when you have a written implementation plan to execute in a separate session with review checkpoints.
Complete project planning and execution framework. Automatically includes all 14 planning sections (planning/0-Master-Index.md through planning/13-Lessons-Learned-Continuous-Improvement.md) plus all 9 Claude Skills (tech-stack-selector, architecture-decisions, code-standards-enforcer, ci-cd-pipeline-builder, agile-executor, project-risk-identifier, automation-orchestrator, webapp-testing, web-artifacts-builder). When installed, all planning templates and execution skills are immediately available.
Runs the Ralph autonomous loop. Executes stories from prds/*.json using git worktrees.
Clarify requirements before implementing by asking the minimum must-have questions. Use when a request is underspecified or ambiguous, when the user asks to “ask clarifying questions”, or when multiple plausible interpretations exist and you risk doing the wrong work.
Complete hour-by-hour checklist for Product Hunt launch day execution. Use this skill to ensure nothing is missed during the critical 24-hour launch window.
Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents
Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.
Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specs - use spec-writing. Not for execution - use speckit-implement.
Plans sprint by selecting items from backlog, defining objective, capacity, and execution order. Use at the beginning of a work cycle to align what will be done.