Loading...
Loading...
Found 212 Skills
Generate a plan for how an agent should accomplish a complex coding task. Use when a user asks for a plan, and optionally when they want to save, find, read, update, or delete plan files in $CODEX_HOME/plans (default ~/.codex/plans).
Create or update `tasks/todo.md` as the prioritised project backlog with clear `feat`/`fix`/`chore` items and ordering. Triggers: new backlog, update todo.md, add backlog item, reprioritise roadmap.
Use when planning work (to create items and tasks), when starting implementation (to mark tasks in-progress), when completing work (to mark tasks done), or to check backlog status. Manages .backlogmd/ for features, bugfixes, refactors, and chores.
Use when you have a spec or requirements for a multi-step task, before touching code
Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use this skill when you need to plan multi-step projects, coordinate agents, or decompose complex user requests into manageable sub-tasks.
Deep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6 hours). Triggers: 'research this', 'deep research', 'discovery', 'explore the space', 'what should I build', 'competitive analysis', 'before I start building', 'research before coding'.
PRD construction for work planning. Compulsory in PLAN phase. Builds .prd file as frozen dependency graph of every possible work item before execution begins. Triggers on any new task, multi-step work, or when gm enters PLAN state.
Route multi-step marketing, product, or business challenges to the right sequence of ClawFu skills. Recommends which frameworks to combine, in what order, with handoff outputs between steps. Use when: planning a product launch end-to-end, combining positioning + offers + launch skills, running a customer-validation sprint, creating a content strategy pipeline, deciding which skills to chain for a complex project, or orchestrating a sales-enablement playbook.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md
Review open issues, selecting an issue to work on, filtering issues by area, pulling GitHub issues, or deciding what to work on next. Triggers include "check issues", "list issues", "what issues", "open issues", "show issues", "view issues", "select issue to work on", "github issues", "backlog issues", "pull issues", "check todos" (deprecated), "list todos" (deprecated), "pending todos" (deprecated).
Insert urgent work as a decimal phase between existing phases, adding mid-milestone work, or creating intermediate phases. Triggers include "insert phase", "add urgent phase", "create decimal phase", "insert between phases", and "urgent work".