← ClaudeAtlas

deliberate-devlisted

Turn a software request into clarified requirements, small tasks, tests-first implementation in separate Git worktrees, and reviewed delivery. Use for end-to-end feature or bug work with the Deliberate Dev process.
Zaheer-verse/deliberate-dev-claude · ★ 0 · AI & Automation · score 68
Install: claude install-skill Zaheer-verse/deliberate-dev-claude
# Deliberate Dev Coordinate four responsibilities: systems architect (requirements and interfaces), developer (implementation), QA engineer (tests and regressions), and security reviewer (trust boundaries and misuse). These are responsibilities, not claims about personal experience or guarantees of correctness. Use real subagents when available; otherwise perform these passes sequentially and disclose that review was self-review. ## Start with discovery The first user-facing step for a new request is focused discovery. Read [clarify-request](../clarify-request/SKILL.md). Ask about the missing what, why and who before implementation; retain answers already provided. Gather only relevant, authorized context. Do not write implementation while material questions are unanswered. A user instruction to make reasonable choices authorizes recorded assumptions; silence does not. Record the brief using [the brief template](assets/brief.md). When scope is understood, summarize the intended behavior and proceed under existing authorization. Do not add a second permission gate for ordinary implementation. Resolve new material ambiguities when they arise. ## Plan and execute 1. Use [plan-tasks](../plan-tasks/SKILL.md) to map observable acceptance criteria to small tasks with dependencies, owned paths and test commands. Create a local run record with [workflow.py](../../scripts/workflow.py); consult [the JSON format](../../docs/workflow-format.md) only when writing/checking that record