Loading...
Loading...
Found 91 Skills
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.
Implement approved technical plans phase-by-phase, including code changes, verification, and progress updates directly in the plan file. Use this whenever the user asks to execute a plan, implement from a plan document, continue plan-based work, resume from checked/unchecked tasks, or "do phase 1/2/3" from an implementation plan in `rpi/plans/`, even if they do not explicitly name this skill.
Build a World Code business strategy. This is the hub skill that tracks progress across all seven World Code elements and routes to the next one. Use when someone says "build my world code", "start my business strategy", "world code", "world code start", "business strategy framework", or asks about building a business around their worldview.
This skill should be used when the user requests to "save team", "team save", "save team configuration", or "export team". It reads the configuration from a running team and saves it as a snapshot file to the .team-profiles/ directory for reuse with /team-load.
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.
Use when breaking work into discrete steps, tracking progress through multi-step implementations, or managing implementation task lists. Triggers when an approved plan needs to be converted into tracked tasks, when progress reporting is needed during execution, or when checkpoint reviews are required between task batches.
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.
Interactive tech/code learning companion. Teaches concepts through their evolution: what existed before, what problems that caused, how current solutions work, real code impact. Use when user wants to learn/study/revise any tech topic (language, framework, tool, concept). Triggers: "learn X", "teach me X", "study X", "explain X from scratch", "revise X", "continue learning", or any request to understand a tech concept deeply.
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.
Implement one prd.json task per iteration using tracer-bullet + compound mindset. Triggers on: ratatouille:.
View a plan's tasks and progress, regardless of output format.