Loading...
Loading...
Found 55 Skills
This skill must be used before any creative work—creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and designs before implementation.
Load Linear issues to initiate tasks, search/list issues, view issue details, and manage issue state using the linear CLI. Use when the user references a Linear issue, wants to start work from Linear, or asks to search Linear.
Use to orchestrate approvals, QA, and go-live steps for SEO content + technical launches.
Manage protocol/standard specifications that define what a system must do. Use to create, import, or update the contract that TASKs implement against.
Transform specifications into actionable implementation plans with phases, tasks, and acceptance criteria. Use when: (1) User asks to create/write an implementation plan, (2) User asks to plan implementation from a specification, (3) Converting specifications from .workflows/specification/{topic}/specification.md into implementation plans, (4) User says 'plan this' or 'create a plan', (5) Need to structure how to build something with phases and concrete steps. Creates plans in .workflows/planning/{topic}/plan.md that can be executed via strict TDD.
Breaks work into bite-sized tasks before coding. Activates when a multi-step task needs planning — creates tasks small enough for a junior developer to follow (2-5 minutes each), with exact file paths, complete implementation details, and verification steps. References Linear issue context and project-specific test commands from CLAUDE.md.
Execute update iterations of existing features (Single Agent Mode). Trigger condition: Requirements or design of completed features change (plan.md + summary.md exist in the directory). Responsible for the complete process from creating update-xxx.md to implementation and review. If the update scale is large and requires multi-role collaboration, create a new Spec and follow the spec-start process.