メニュー
Use when starting a multi-phase feature and need the ordered skill pipeline from product context through plan, build, documentation sync, and PR. Use when unsure which skill runs when or how much context to pass at each step.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | initiative-workflow |
| description | Use when starting a multi-phase feature and need the ordered skill pipeline from product context through plan, build, documentation sync, and PR. Use when unsure which skill runs when or how much context to pass at each step. |
| disable-model-invocation | true |
End-to-end order for a planned feature in this repo. Each step uses one skill; do not merge steps into one mega-prompt.
flowchart LR
P[planning-workflow]
B[builder-workflow]
D[documentation-sync]
G[git-pr-workflow]
P --> B --> D --> G
Repeat B → D → G for each plan phase (each PR).
When: Outcome or UX is still fuzzy.
How: Short chat (or brainstorming skill from superpowers cache) — problem, users, constraints, non-goals.
Output: Bullets the planner pastes into the plan’s summary / Phase 1 design agreement. Not a substitute for the plan file.
When: Multi-package work, phases, or “plan first.”
Output: .cursor/plans/<slug>.plan.md (approved by you).
Plan must include per phase:
| Section | Owner skill |
|---|---|
| Code/config surfaces, scouts, verify commands | builder-workflow |
| Documentation before PR (path list) | documentation-sync — after build, not during |
Your message (minimal):
Use planning-workflow.
Goal: …
Constraints: …
Phases: … (one PR per phase if applicable)
When: Plan approved; execute one phase.
Scope: Code and config only — no docs/, AGENTS.md, README.md, .cursor/skills/ edits unless the plan labels a docs-only phase.
Ends at: Checkup PASS + code review critical fixes fixed. Does not commit (unless you explicitly ask).
Your message (minimal):
@.cursor/plans/<slug>.plan.md
Use builder-workflow. Execute Phase N only.
Do not edit documentation tiers; those are step 4.
Do not attach: rules bodies, full product spec, scout tables from prior runs.
When: Phase build is finished (verify gate passed on code/config). Before any commit or PR for that phase.
Not: During scout/implement/checkup. Not interleaved with implementer slices.
Input: Plan section Documentation before PR for that phase + current branch diff.
Your message (minimal):
Build for Phase N is complete (checkup passed).
Use documentation-sync for paths listed in .cursor/plans/<slug>.plan.md Phase N "Documentation before PR".
When: Code and docs for the phase are done; ready to commit and open PR.
Prerequisite: Step 4 finished (docs match code).
Your message (minimal):
Use git-pr-workflow. Commit Phase N, push, open draft PR.
[ ] Plan approved (.cursor/plans/….plan.md)
[ ] builder-workflow Phase N — checkup PASS (code/config only)
[ ] documentation-sync — plan’s doc list updated
[ ] git-pr-workflow — commit, push, PR
[ ] Merge or continue to Phase N+1
| Step | Paste |
|---|---|
| Planning | Goal, constraints, phase count |
| Builder | Plan path + phase number + execute |
| Doc sync | Plan path + “Phase N doc list” + build complete |
| Git/PR | Branch intent, draft vs ready, phase scope |
| Skill | Role |
|---|---|
| planning-workflow | Write plan |
| builder-workflow | Execute phase (subagents) |
| documentation-sync | Docs after build, before PR |
| git-pr-workflow | Commit, push, PR |
Use after builder-workflow checkup passes for a plan phase and before git-pr-workflow, to sync docs/AGENTS/README/skills with code per the plan Documentation before PR list. Not during builder implement.
Use when an approved plan phase should be built (code/config only) via subagents through checkup and review, stopping before documentation-sync and git-pr. Use as step 2 of initiative-workflow.
Use when multi-step or cross-package work needs a written plan before coding, when the user asks for phases/PRs/impact map, or when producing `.cursor/plans/*.plan.md` with code and doc-before-PR sections. Use as step 1 of initiative-workflow.
Monobun ship path — bun overall, working tree, branch gate, staged diff, context-aware conventional commit, precommit, push, and PR body from .github/pull_request_template.md (not fill-only). Use when the user asks to commit, push, open a PR, or finish a branch.
Bun entry scripts under tools/scripts/<area>/ with subcommands, node:util parseArgs, Ink step progress (Static + spinner), renderAndExit, and quiet mode without duplicate logic. Use when adding or refactoring repo CLI scripts, local/dev/prod commands, postinstall hooks, or anything mirroring tools/scripts/local/.