Loading...
Loading...
Found 31 Skills
Use this skill when planning, executing, or recovering software projects with a focus on risk management, dependency tracking, and stakeholder communication. Triggers on project planning, risk assessment, dependency mapping, status reporting, milestone tracking, stakeholder updates, escalation decisions, timeline estimation, resource allocation, and project recovery. Covers RAID logs, critical path analysis, and communication cadences.
Execute implementation plans with checkpoint validation, progress tracking, and quality gates. Use for task implementation, plan execution, progress tracking. Skip if no plan exists.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
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.
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]
Runs the Ralph autonomous loop. Executes stories from prds/*.json using git worktrees.
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.
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.
Use this when you have a written implementation plan and execute it in separate sessions with review checkpoints
Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents