メニュー
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | change-request |
| model | sonnet |
| description | Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization. |
HARD GATE —
specs/release-plan.yamlmust exist before running either mode. If it doesn't, runplan-releasefirst.→ verify:
[ -f specs/release-plan.yaml ] && echo "ready" || echo "BLOCKED: run plan-release first"
Two modes. State which one you want or the skill will ask.
Intake a new requirement mid-flight without disrupting work in progress.
specs/epics/ does it affect or replace?tasks[] with Gherkin-style AC in epic YAML (each task has verify). Tag requirement deltas: ADDED / MODIFIED / REMOVED / RENAMED with before/after for non-ADDED changes (e45s29).specs/epics/eNN-slug.yaml and register in release-plan.yaml epics[].→ verify: grep -c 'stories:' specs/epics/*/epic.yaml
Value-engineering pass over the full release using WSJF.
See REFERENCE.md for the full WSJF scoring rubric.
release-plan.yaml epics[] and per-epic wsjf fields.specs/release-plan.yaml and epic wsjf keys with rationale.→ verify: grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml
If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
specs/epics/ the request affects or replaces.Run bash scripts/sync-status-from-epics.sh. Suggest plan-work or build-epic for the top-ranked unstarted story.
Weighted Shortest Job First: WSJF = (Business Value + Time Criticality + Risk Reduction) / Job Size
All dimensions scored 1–10 using a Fibonacci-like scale: 1, 2, 3, 5, 8, 10.
| Score | Meaning |
|---|---|
| 10 | Core revenue path, legal requirement, blocking launch |
| 8 | Significant user value, major pain point removed |
| 5 | Notable improvement, medium user segment affected |
| 3 | Nice-to-have, minor convenience |
| 1 | Cosmetic or speculative |
| Score | Meaning |
|---|---|
| 10 | Hard deadline (regulatory, contract, launch date) |
| 8 | Competitive window closing, partner dependency |
| 5 | Would delay next milestone if deferred |
| 3 | Flexible, can slip one sprint |
| 1 | No urgency |
| Score | Meaning |
|---|---|
| 10 | Eliminates critical architectural risk or enables a new capability |
| 8 | Reduces a known failure mode or unblocks high-value work |
| 5 | Moderate risk mitigation or enablement |
| 3 | Low risk reduction |
| 1 | No risk relevance |
| Score | Meaning |
|---|---|
| 1 | Hours |
| 2 | 1 day |
| 3 | 2–3 days |
| 5 | 1 week |
| 8 | 2 weeks |
| 10 | 1 month+ |
Stories with WSJF < 1.5 are cut candidates: high effort, low combined value.
Story: "Add OAuth login"
WSJF = (8 + 5 + 3) / 5 = 3.2 — healthy, implement early.
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.
Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn "I want X" into a concrete spec.
Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap.
Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions "grill me". For doc-grounded variant, use grill-with-docs.
Block dangerous git commands (push, force push, reset --hard, clean, branch -D, checkout/restore .) and enforce Conventional Commits & Branch Protection before an AI agent runs them. Installs hook scripts for Claude Code, Cursor, Cursor CLI, and Gemini CLI; documents Google Antigravity Terminal deny lists. Use when the user wants git safety hooks, to block git push or destructive git in agents, or to mirror the same policy across AI coding tools.