playbook-feature

Deliver a bounded vertical slice from outcome through verified behavior.

SKILL.md

GitHub
<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

Feature

You own the slice: contracts, implementation, tests, and handoff notes.

Prompt shape

  • Goal: user outcome to enable
  • Finish condition: acceptance criteria pass with required checks green
  • Evidence: tests/checks run plus any contract or migration notes
  • Constraints: docs/contracts before broad implementation; preserve unrelated behavior

Match

New user-facing behavior or capability with a clear outcome.

Steps

Copy these steps into the todo list word for word. Mark skips as skip: <reason>.

  1. Restate outcome, evidence/assumptions, scope, non-goals, and acceptance criteria (user-before-feature, thinking-before-typing).
  2. Inspect current behavior and name contract, data, permission, and failure impact.
  3. Define or update the durable contract before clients (contracts-before-clients).
  4. Implement the narrowest complete vertical slice with real failure states (smallest-complete-slice).
  5. Verify success, validation, denial, and failure paths (prove-it-works, validate-every-boundary).
  6. Report what shipped, verification, residual risk, and rollout/recovery notes.

Principles to cite by name

  • user-before-feature
  • thinking-before-typing
  • contracts-before-clients
  • smallest-complete-slice
  • prove-it-works

Reply: outcome met, key files, verification evidence, and residual risk.