Full-stack feature: requirements to user docs in one session

Feature SDLC is the longest built-in workflow. Use it for a feature that crosses the stack and that you want designed, built and documented in one pass, with a single change to review at the end.

Which agents run

After the eight steps, the code pass writes the change from the team's output. Your project's test command runs against it in a sandbox, and the AI review records findings on the real diff. The Delivery plan step also adds its items to the Plan board.

Gates before the pull request

• Tests on the current version. Failing tests block. If someone edits the change after its tests ran, the old result no longer counts and the change shows as untested.
• Findings. Open high or critical findings block until they are triaged. If the review can't finish, the change is held until you re-run.
• Approval. Someone other than the person who started the session approves, whenever the workspace has another approver.

Hold it for a person before it starts

Eight steps cost more than four. This policy rule makes every Feature SDLC session wait for an approval before anything is spent:

{
  "id": "approve-feature-sdlc",
  "action": "workflow.dispatch",
  "resource": "feature-sdlc",
  "decision": "ask",
  "description": "A person approves before an eight-step feature session starts"
}

The session waits as held under Review & Gate → Approvals. A held start expires after 3 days, and a rejection cancels it. Pair the rule with a per-workflow cap in cost controls.

Keep the scope to one pull request

The code pass writes at most 25 files in one change and reads a fixed amount of the team's output, so in an eight-step run the last steps can be cut from what it sees. Pick a feature that fits in one pull request: one endpoint, one screen, one guide. For bigger work, spec it first with the feature spec template, then build phase by phase with follow-up sessions, each starting from the unmerged change before it.