← ClaudeAtlas

ss-coding-workflowlisted

Executes a ready-made plan or a plain-language change instruction end to end — branch, multi-agent coding with built-in review, and PR/commit delivery. Use for running an existing execution plan or a simple, well-scoped code change; use ss-feature-workflow instead when a proposal and plan still need to be drafted.
lbk-open/super-spec · ★ 1 · AI & Automation · score 65
Install: claude install-skill lbk-open/super-spec
# Coding Workflow Chains the existing `ss-*` skills into a single execute-and-deliver flow: ``` ss-create-branch → ss-coding (built-in review) → review-acceptance loop → ss-create-pr ``` **Core principle: thin orchestration.** This skill never writes code itself. It calls the other skills in order, passes outputs along, and reports progress. > **Review is not run twice.** `ss-coding` already enforces a post-coding review > internally and returns a verdict. This workflow never invokes `ss-code-review` separately — > the review-acceptance loop below is driven entirely by that verdict. Unlike `ss-feature-workflow`, there is no proposal or planning step here, and no manual gate by default — the input is either an already-prepared plan or a change instruction handed straight to coding. ## When to Run This is end-to-end orchestration: it creates a branch, spawns coding agents, runs reviews, and delivers the result. Only run it when the user explicitly asks for this skill or clearly wants the full execute-to-delivery pipeline. For an ordinary edit, a question, or a single-step request, do the work directly (or point to the one relevant `ss-*` skill). ## Inputs - **Execution input**, one of: - a path to an existing execution plan (produced by `ss-plan`), or - a plain-language change instruction (e.g., "extract OrderService's helper methods into OrderUtils"). If ambiguous which one it is, ask; when deciding autonomously, treat text with a recognizable task/file st