Loading...
Loading...
Found 66 Skills
Serial collaborative planning with Plan Note - Multi-domain serial task generation, unified plan-note.md, conflict detection. No agent delegation.
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.
Create handoff + enter plan mode for next session. Use when user says "forward", "handoff", "wrap up", or before ending session.
Creates task management documentation (docs/tasks/README.md + kanban_board.md). L2 Worker in ln-100-documents-pipeline. Sets up Linear integration and task tracking rules.
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.
Query and manage Linear issues, cycles, labels, documents, attachments, projects, and team workflows. Use when creating, updating, searching, or triaging Linear issues, managing sprints, checking project status, or running a standup summary.
Use when a technical question needs a real experiment to answer, to generate a structured spike spec before executing it in a separate session
Discussion entry when ideas are still vague — first conduct triage through 1-2 rounds of dialogue to determine which downstream process this discussion should eventually go to: if the idea is clear enough, proceed directly to feature-design; if the direction of a small requirement is set, continue the discussion within the feature and document it in `{slug}-brainstorm.md`; if a large requirement cannot fit into a single feature, hand it over to roadmap for decomposition. The role of AI is a thinking partner, not a recorder — dig out the real problem the user wants to solve, proactively evaluate when the user brings a solution, and propose alternative directions when necessary. Trigger scenarios: when the user says "I have an idea that's not clear yet", "Let's brainstorm first", "I want to do something but it's still vague", "Let's talk about this area", "The function direction is still undecided", or when the user comes with a specific solution but wants to hear other ideas first. Bugs (go to issue) and refactoring (go to refactor) are not handled here.
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.
Analyze a project's past Codex sessions, memory files, and existing local skills to recommend the highest-value skills to create or update. Use when a user asks what skills a project needs, wants skill ideas grounded in real project history, wants an audit of current project-local skills, or wants recommendations for updating stale or incomplete skills instead of creating duplicates.
Design-driven development methodology. The design/ directory is the single source of architectural truth — read it before coding, stay within its boundaries, and when the system's shape needs to change, update the design first. Use this skill whenever starting any development work on this project. Also use when the user asks to: create or update architecture docs, add a new module or feature that might cross existing boundaries, refactor system structure, or understand the codebase architecture. Trigger on phrases like "design first", "update the design", "does this change the architecture", "write a design for", "what's the current design", or when onboarding to understand a codebase's shape. Supports arguments: `/design-driven init` to configure a project for design-driven development, `/design-driven bootstrap` to generate design from an existing codebase.
[Utilities] ⚡⚡⚡⚡⚡ Bootstrap a new project step by step