Fully autonomous SDLC pipeline — zero user intervention. Opus 4.6 runs the entire workflow from plan through PR, handles review feedback loops, and stops only when the PR is ready for human merge. Use this skill whenever the user says "/flow-auto", "auto flow", "autonomous flow", "just do everything", "full auto", "hands off", "run it all", or any request to run the complete pipeline without checkpoints or user decisions. Also triggers on "no intervention", "auto pipeline", "unattended flow", "fire and forget flow", "do everything and leave me a PR", or "I'm going to sleep just build it". This is the zero-touch version of /flow — same pipeline, no pauses. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.
Fully autonomous SDLC pipeline in an isolated git worktree — zero user intervention, zero git conflicts with other terminals. Creates a lightweight worktree (no Herd URL, no VS Code, no SSL), runs the full flow-auto pipeline inside it, and stops when the PR is ready for merge. Use this skill whenever the user says "/flow-auto-wt", "auto flow worktree", "parallel flow-auto", "flow-auto in worktree", or any request to run the autonomous pipeline in an isolated worktree. Also triggers on "isolated flow-auto", "worktree auto", "parallel auto", "run flow-auto in isolation", "don't touch my branch", "run in parallel", "parallel pipeline", or when running multiple flow-auto instances on the same repo. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.
Create structured implementation plans with git branches and memory search. Use this skill whenever the user wants to plan a feature, fix, refactor, or any development task. Triggers on: "/plan", "plan this", "create a plan for", "let's plan", "I need to plan", "break this into phases", "how should we approach", "let's think about how to build", or any request that involves planning, phasing, or strategizing before coding. For worktree-based plans (isolated directory), use /plan-wt instead. ALWAYS use this skill before starting implementation — planning first, coding second.
Initialize a new project with GitHub Actions, git hooks, blueprint workspace, CLAUDE.md, and branches. Use this skill whenever the user says "/start", "initialize project", "setup project", "start new project", or any request to set up the standard development workflow in a repo. Also triggers on "project init", "bootstrap project", "setup hooks", or "initialize repo". Sets up everything: claude-pr-reviewer.yml + tests.yml actions, commit hooks, blueprint/ workspace, CLAUDE.md, configurable staging branch. Updates are handled by `blueprint update` — no separate sync skills needed.
Capture, manage, and promote pre-planning ideas before they become full plans. Use this skill whenever the user says "/backlog", "add to backlog", "backlog idea", "capture this idea", "save this for later", "I had an idea", or any request to manage the idea backlog. Also triggers on "list ideas", "promote idea", "backlog list", "drop idea", "mark done", "what's in the backlog", "show me the ideas", "pending ideas", or any request to add/view/promote/done/drop items in blueprint/backlog/. The backlog is the pre-planning stage — ideas live here until promoted to /plan. Even if the user doesn't explicitly say "backlog", trigger when they describe wanting to capture a feature idea, task, or improvement for later without implementing it now. This skill is the gateway to the SDLC — nothing gets planned or built without first passing through the backlog.
Show quick repo status — branch, base, plan, PR info in one shot. Triggers on "/bp-status", "/status", "show status", "repo status", "what branch am I on", "current status", "where am I", "project status", "what's the current state", "which branch", "is there a PR open", "what plan am I on". Uses blueprint CLI with git fallback.
Review, validate, and prepare a plan for optimal execution by subagents or coordinated teams. And also Assign Execution Plan — this skill both validates the plan AND determines the execution strategy (parallel subagents, teams, mixed dispatch), marks task complexity ([H]/[S]/[O]), and commits the reviewed plan with its assigned execution mode. Use this skill whenever the user says "/plan-review", "review the plan", "prepare plan for execution", "optimize the plan", "is the plan ready", "plan readiness", or any request to validate and prepare an existing plan before implementation. Also triggers on "mark complexity", "execution strategy", "plan delegation", or "prepare for plan-approved". ALWAYS use this skill after /plan and before /plan-approved — it's the pre-flight check that makes execution fast. Do NOT use for post-implementation audits — use /plan-check for "check the plan" or "audit the plan". With 1M context, small/medium plans (≤15 tasks) can flow directly into /plan-approved without clearing context
Fetch PR review comments, categorize feedback, implement fixes, and push. Use this skill whenever the user says "/address-pr", "address review", "fix review comments", "handle PR feedback", or any request to implement fixes based on PR review feedback. Also triggers on "fix the review", "address feedback", "implement review changes", "implement the requested changes", or "handle review comments". Fetches real comments via blueprint pr-review.