| name | run-dev-graph-decompose |
| description | 大きな自然文構想を feature・architecture・機能間依存へマクロ分解したいとき、ready feature の system-dev-planner package を atomic 登録・binding 別投影したいときに使う。 |
| version | 0.1.0 |
| owner | harness maintainers |
| source | plugin-plans/dev-graph/component-inventory.json#C14 |
| kind | run |
| prefix | run |
| hierarchy | L1 |
| user-invocable | true |
| argument-hint | <want|--package PATH> [--repo-root PATH] [--manual-plan] [--dry-run] |
| allowed-tools | ["Read","Write","Bash","Skill","AskUserQuestion","Agent"] |
| script_refs | ["../../scripts/resolve-repo-context.py","../../scripts/validate-graph-schema.py","../../scripts/gh-bridge.py","../../scripts/bd-bridge.py"] |
| schema_refs | ["../../schemas/graph-node.schema.json"] |
| reference_refs | ["../../../system-dev-planner/references/feature-execution-package-contract.md","../../references/execution-tracker-contract.md"] |
| responsibility_refs | ["prompts/R1-elicit.md","prompts/R2-plan.md","prompts/R2b-feature-planning.md","prompts/R3-decompose.md","prompts/R4-project.md","prompts/R6-dryrun.md"] |
| responsibilities | [{"id":"R1-elicit","name":"elicit","prompt_required":true,"summary":"自然文の「やりたいこと(大)」とマクロ分解の粒度基準 (feature単位)・機能間依存推定方針、および --dry-run 指定の有無をヒアリングして確定する"},{"id":"R2-plan","name":"plan","prompt_required":true,"summary":"自然文のwantからfeatureノード群+architectureノード+機能間depends_onへのマクロ分解案を組み立てる (1機能=13タスク仕様書への細分解はsystem-dev-plannerへ委譲しここでは行わない)"},{"id":"R2b-feature-planning","name":"feature-planning","prompt_required":true,"summary":"ready featureごとにsystem-dev-plannerを起動し、返却packageがP01..P13 exact 13 task/13-node DAG、共通parent_feature/feature_package_idを満たす場合だけC02へ渡す。手動/system-dev-planも同じ検査経路を通す"},{"id":"R3-decompose","name":"decompose","prompt_required":true,"summary":"C02で全feature/task (system-dev-planner/`/system-dev-plan`が返すpromoted task含む) のbinding/path/dependency/parent_featureを事前検証してall-or-none登録する。eligible taskをbinding=beadsならC28 create/dep-add、githubならC12 Issue、noneなら外部writeなしへ振り分け、既存linkageは再起票しない"},{"id":"R4-project","name":"project","prompt_required":true,"summary":"tracker_binding=githubかつissue_and_projectsのtaskだけをconfigured Projectsへ冪等追加し、Statusはlocal_to_projectで初期化する。beads mirrorとnoneはProject mutationしない"},{"id":"R5-retry","name":"retry","prompt_required":false,"summary":"Issue成功後のProject mutation失敗はローカルtask/Issue linkageを維持し、alias単位のsync_state=pending_retryとして次回C03 syncへ渡す"},{"id":"R6-dryrun","name":"dryrun","prompt_required":true,"summary":"--dry-run時はIssue/Project mutationを一切実行せず、Issue body、Project targets、field valuesのpreviewだけを返す"}] |
| combinators | ["with-goal-seek","with-feedback-contract"] |
| goal_seek | {"engine":"inline","fork":"subagent","max_loops":5} |
| completeness_exempt | ["manifest: goal_seek.engine=inline が未達 checklist から実行局面を都度選ぶため、固定 phase の workflow-manifest.json は適用外。停止条件と配線は本文 ## ゴールシーク実行を正本とする。"] |
| feedback_contract | {"max_iterations":3,"criteria":[{"id":"IN1","loop_scope":"inner","text":"validate-graph-schema.py で分解生成ノードを送信前検証しスキーマの必須キー欠落が 0 件","verify_by":"script"},{"id":"OUT1","loop_scope":"outer","text":"マクロ分解結果 (feature+architecture+機能間depends_on) のDAGが循環なし・粒度閾値内で、評価前draftはIssue起票0件、confirmed/pass/readiness completeへの昇格後だけ起票対象になる","verify_by":"live-trial"},{"id":"OUT2","loop_scope":"outer","text":"同一入力を二回実行してもbinding=beadsはbd issue/blocks edge、binding=githubはIssue/Project item、binding=noneはlocal nodeだけを各1組維持する","verify_by":"test"},{"id":"OUT3","loop_scope":"outer","text":"--dry-run時にlocal graph/Beads/GitHub/Projects writeが0件のままbinding解決と投影差分だけがpreviewされる","verify_by":"test"},{"id":"OUT4","loop_scope":"outer","text":"mode=both+auto、github+local_only、beads+Issue publicationを各fixtureでfail-closedし、外部write 0件となる","verify_by":"test"},{"id":"OUT5","loop_scope":"outer","text":"local batch成功後の外部mutation失敗でlocal taskを維持し、失敗node/operationだけpending_retryから冪等再実行できる","verify_by":"test"},{"id":"OUT6","loop_scope":"outer","text":"同一ready featureへの自動起動を二回実行してもP01..P13 exact 13 taskが一組だけ維持され、全taskのparent_feature/feature_package_idが一致する","verify_by":"test"},{"id":"OUT7","loop_scope":"outer","text":"同一featureに対する自動起動結果と手動`/system-dev-plan`実行結果は同じparent_featureで登録され、経路の違いによる二重登録が生じない","verify_by":"test"}]} |
