Coordinated Feature — Fast Path

For coordinated changes scoped to hours: one in-chat plan, then code. The enemy is ceremony — no design docs, no multi-phase process, no summary documents afterwards. This file is the whole workflow: load no other dev-* skill unless a step below names it, and run no review, second opinion, or reviewer subagent unless the user or the repository's instructions ask for one.

Downgrade instead to dev-feature-lite when the behavior and implementation path are obvious and the change can proceed without a plan or user decision.

Escalate instead when the task smells bigger: unknown root cause → dev-debug; multiple viable architectures or "how should we..." → dev-problem-solving. Say you're escalating and why, in one line.

Step 1 — Clarify (only if genuinely needed)

Skip this step when nothing is ambiguous. Otherwise ask at most 3 questions in one batch, each with a recommended answer the user can approve in one word, and only about what changes the implementation:

• Concerns that fork the design: "should this be per-user or global?"
• Tool/library choices when the codebase shows no precedent
• Behavior at a boundary the request doesn't cover: "what happens on duplicate?"

Look up facts and conventions in the code instead of asking; put obvious defaults in the plan's assumptions; skip preferences that don't change the diff.

Step 2 — Plan (one short in-chat message, then go)