repo-orchestration
RepoSkillOpt — To-Be Design & Implementation Orchestration (Canonical Skill)
Purpose
This skill consumes the as-is artifacts (Architecture View + Change-Impact Analysis) and a stated goal, and produces (a) a reviewable target-state design — ADRs + a concise Design Doc grounded in the as-is evidence — and (b) an implementation orchestration plan: a machine-readable Task Ledger decomposed into small, independent, individually acceptance-tested sub-tasks with declared dependencies and a topological order. The plan is an artifact, not an executor — any orchestrator can drive it; this skill never executes the implementation. Vendor-neutral: no dependency on any particular coding-agent runtime.
Trigger Conditions
Activate when the user asks to design a target state / to-be, plan the work / decompose into tasks, or produce an implementation plan for goal X — or recognizable equivalents. Do not activate for unrelated requests, and do not execute the resulting plan.