Spec-driven software engineering for AI coding agents - a Python CLI that drives a brainstorm, spec, plan, execute loop over markdown artifacts on disk.
Skill Claude CodeCodex
Use when the user wants an unattended specflo run — "auto mode", "autopilot", "run it on its own", "keep going without me", "don't stop to ask" — map that to specflo auto. It is an explicit, per-invocation opt-in that drives the pipeline across phase boundaries without the ask-first pause. Do NOT use for the normal…
Skill Claude CodeCodex
Use at the start of a specflo project's brainstorm phase, when turning a fuzzy idea into a captured, validated understanding before any spec or code. Triggers include "let's figure out what we're building", "brainstorm X", or specflo status showing the brainstorm phase. Do NOT use for trivial fixes or when a…
Skill Claude CodeCodex
Use at a specflo project's execute phase, when turning a validated plan.md into committed, verified code one task at a time. Triggers include "execute the plan", "start building", "work the next task", or specflo status showing the execute phase. Do NOT use before a plan has been validated, or for trivial fixes…
Skill Claude CodeCodex
Use at a specflo project's plan phase, when turning a validated spec into a dependency-ordered, testable task plan before any code. Triggers include "write the plan", "break this into tasks", or specflo status showing the plan phase. Do NOT use for trivial fixes or before a spec has been validated.
Skill Claude Code
Use when a specflo brainstorm needs grounding in current facts — an upfront landscape scan of what already exists (tools, SDKs, libraries, competitors, reference implementations, framework state), or a targeted check of a fact-dependent assumption before it becomes a decision. Dispatched as a subagent by the…
Skill Claude CodeCodex
Use when the user signals they want to set the active specflo project aside ("we're done with this", "drop this", "not worth it", "shelve it", "park this for now") — map that to specflo shelve — or to pick a paused project back up ("let's pick that back up", "resume that", "un-shelve it") — map that to specflo resume.…
Skill Claude CodeCodex
Use at a specflo project's spec phase, when turning a validated brainstorm into a structured, testable spec before any plan or code. Triggers include "write the spec", "let's spec this out", or specflo status showing the spec phase. Do NOT use for trivial fixes or before a brainstorm has been validated.
Skill Claude CodeCodex
Use when driving pi subagents through the specflo agent CLI - starting a headless pi worker, sending it prompts, monitoring it, and stopping it. Triggers include "start a pi agent", "delegate this to a pi subagent", "prompt the agent", or an orchestration plan that hands tasks to specflo agent workers. Do NOT use for…
Skill Claude CodeCodex
Use when the active specflo project is at harden level (specflo status shows the harden level), or the user asks to harden code that already exists through specflo ("harden this module", "shake the bugs out of X", "review and fix it until it is clean"). Works one brief that names the scope, runs fresh-context harden…
Skill Claude CodeCodex
Use when the active specflo project is at quick level (specflo status shows the quick level), or the user asks for a quick, small change through specflo ("just fix it", "quick one", "small tweak"). Works one brief.md with a goal, one check and proof, then completes the project. Do NOT use for fast or full level…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: