Loading...
Loading...
Found 314 Skills
Converge vague requirements into a goal contract (scope / non-goals / success criteria / verification / stop conditions) that another AI can execute autonomously and be accepted. This skill only writes goal contracts, **never executes tasks for users**. Hard trigger condition: This goal is to be handed over to others for execution — subagent, Codex, another AI session, or another person. It is used to write goals, optimize goals, revise handoff prompts, or turn requests like "finish today, optimize as much as possible, help me research and execute" into task contracts that the executor won't guess randomly or overstep boundaries. Not applicable to: internal team requirement management and version breakdown (use issue-pool — it produces tasks for humans to start working on, not contracts for AI), interface design exploration (use design-exploration), PRD/acceptance criteria/test case documents (use prd-test-writer), framework planning and version roadmaps (use issue-pool), and situations where the user actually wants you to **do the task directly** — just do it directly instead of using this skill to turn the task into a document.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Turn a SPEC, PRD, or any stated goal into a high-level executable PLAN of outcome-shaped tasks, and regenerate that plan when execution reveals it is wrong. Use this skill whenever the user asks to plan, break down, decompose, sequence, or roadmap work from a spec/requirements document or a goal, and whenever an executor's replan gate fires because a task's postcondition failed, expected state does not exist, a planned task is impossible, or new information invalidates a later task. Runs in two modes, initial planning and replanning, and always produces the same PLAN.md format.
Graph engineering for parallel task execution: convert a task, PRD, SPEC, or issue set into a dependency graph (DAG), layer it into supersteps, then implement each independent node concurrently with subagents — each node runs /goal → /review-it → /ship-it in an isolated git worktree, with a fan-in barrier between waves. Triggers on: graph, graph engineering, build a graph, task graph, dependency graph, DAG, parallel implement, 并发实现, 并行实现, 任务图, 把任务变成图, fan-out fan-in, superstep, dynamic workflow.
Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Scaffold, status-check, and manage specification directories. Handles auto-incrementing IDs, README tracking, phase transitions, and decision logging in docs/specs/. Used by both specify and implement workflows.
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
One-stop creation of SecondMe integration projects, executing initialization, requirement definition, and project generation in sequence
Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user stories, modeling business processes, or translating business needs to technical specs.
Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.