ss-feature-workflow

Feature Workflow

Chains the existing ss-* skills into one requirement-to-delivery pipeline:

ss-create-branch → [complexity triage]
  complex → ss-proposal → [Gate: proposal approval] → ss-plan
  simple  → ss-plan
→ ss-coding (built-in review) → review-acceptance loop → ss-create-pr

Core principle: thin orchestration. This skill never writes code or drafts a proposal/plan itself. It calls the other skills in order, pauses at the gates below, passes each step's output to the next, and reports progress. Every step's logic stays owned by its own skill.

Review is not run twice. ss-coding already enforces a post-coding review internally (with its own fix rounds) and returns a verdict. This workflow never invokes ss-code-review separately — the review-acceptance loop below is driven entirely by the verdict ss-coding returns.

When to Run

This is heavy, end-to-end orchestration: it creates a branch, writes a proposal, spawns multiple coding agents, runs reviews, and opens a PR. Only run it when the user explicitly asks for this skill or clearly wants the full feature pipeline. For an ordinary edit, a question, or a single-step request, do the work directly (or point to the one relevant ss-* skill) — only mention this workflow if the user might want the full pipeline.

Inputs

• Requirement source — a PRD/requirement document link, a plain-text requirement description, or a local requirement file. If missing, ask for one before proceeding.
• Delivery mode — full (default) or lite. See "Delivery Mode" below.
• Proposal preference — force or skip the proposal stage, overriding the complexity triage below.
• Skip-gates — proceed through the proposal-approval gate without pausing.
• Decide-autonomously — resolve ambiguous choices without asking, instead of pausing for clarification.
• Worktree preference — develop in an isolated worktree, or in place. Forwarded to ss-create-branch; omit to let it decide or ask.