/dev
ImplementationModel-invoked

Build from a PRD, design spec, or agent brief: climb the solution ladder, write tests at the seams you confirmed, keep scope honest, and debug with a tight loop.

When to use

The spec is ready (`ready-for-agent` issue, PRD, or `docs/design/`). Pick up one vertical slice at a time.

Prerequisites

  • A ready spec: PRD, `docs/design/`, or `ready-for-agent` brief.
  • One vertical slice — not the whole epic at once.

How to use

  1. Invoke /dev (or ask to use the `developer` agent) with the spec path or issue.
  2. Confirm seams and climb the solution ladder before writing production code.
  3. Expect TDD at the seams you confirmed — tests first where the skill requires it.
  4. When the slice is green, run /code-review before merge.

Done when

The vertical slice is implemented with tests at confirmed seams and ready for /code-review.

Pipeline

Upstream
/design or agent brief from /triage
Downstream
/code-review

Boundaries

Does not write requirements or UI specs. Pre-merge review is /code-review, not part of the /dev loop.

Tips

  • Do not invent requirements mid-flight — escalate to /reqs or /align.
  • Deploy/CI breakage is /devops, not a feature /dev pass.

Sample prompt

prompt
/dev

[feature] — docs/prd/feature-x.md

Agent

PRINCIPAL ENGINEER

Owns: production code, TDD, solution ladder, scope self-check, status report, debugging

Use the developer to implement [feature] from spec
developer
← Skill catalog