decomposing-tasks
Use when you have a complete feature spec and need to plan implementation - analyzes task dependencies, groups into sequential/parallel phases, validates task quality (no XL tasks, explicit files), and calculates parallelization time savings
scrum-event-sprint-execution
Execute Sprint with inspect-and-adapt cycles. Use when implementing subtasks, adapting plans based on progress, or managing sprint execution.
dev-swarm-stage-personas
Create/Update detailed user personas and user stories based on market research and business requirements. Use when starting stage 02 (personas) or when user asks to create/update personas, user stories, or user journey maps.
scrum-team-product-owner
AI-Agentic Product Owner accountable for maximizing product value through effective Product Backlog management. Use when creating PBIs, ordering backlog, or accepting sprints.
project-organization
Expert guidance for setting up and organizing research software projects following Sam Abbott's established patterns for R packages, Julia packages, and research projects
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
todo-files
Manage TODO files as persistent working memory for complex patterns. Track design decisions, implementation progress, and context across sessions. Use when starting complex patterns or resuming multi-session development work.
golang-pro
Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.
coordination
Multi-agent coordination for parallel plan execution with the coordinate and coord_output tools.
builder-role-skill
Professional software implementation skill for building features, components, and systems through multi-phase TDD development and incremental delivery.
technical-review
Validate completed implementation against plan tasks and acceptance criteria. Use when: (1) Implementation is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
page-estimation
This skill provides screenplay page count and runtime estimation formulas. Covers the page-to-screen rule (1 page = 1 minute), genre adjustments, target lengths for features vs shorts, and element-based calculations. Use when: estimating screenplay length, calculating runtime, tracking page count, or validating target length for submission requirements.
dev-swarm-code-development
Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document. Use when implementing features, changes, bug fixes, or improvements.
product-manager
This skill should be used when users request new features, improvements, fixes, or ask to create plans. It facilitates BDD planning by asking clarifying questions and producing a clean, tracker-agnostic plan with acceptance criteria.
reality-check
Find the gaps in your plan before your stakeholders do. Pressure tests plans, strategies, and communications. Domain-smart advisor, not nitpicker.
dev-swarm-stage-sprints
Plan and execute agile development sprints, breaking down product requirements into manageable backlogs with clear acceptance criteria and test plans. Use when starting stage 09 (sprints) or when user asks about sprint planning or backlog creation.
page-estimation
This skill provides screenplay page count and runtime estimation formulas. Covers the page-to-screen rule (1 page = 1 minute), genre adjustments, target lengths for features vs shorts, and element-based calculations. Use when: estimating screenplay length, calculating runtime, tracking page count, or validating target length for submission requirements.
dev-swarm-code-review
Review and audit code quality, architecture, and implementation. Verify code meets design specs, find bugs, identify improvements, and create change/bug/improve backlogs. Use when reviewing completed code, auditing implementations, or ensuring quality.
technical-orientation
Explain technical projects, codebases, tools, or documentation to a non-engineer. Use when the user says "orient me", "explain this repo", "what does this do", "get me up to speed", "break this down for me", or shares a GitHub URL asking for explanation. Also use when a non-technical person needs to understand something technical quickly.