← ClaudeAtlas

featurelisted

Guided feature development — brainstorm, explore codebase, design architecture, implement with TDD, and review. Use for new features or significant changes.
kdlbs/kandev · ★ 304 · Code & Development · score 83
Install: claude install-skill kdlbs/kandev
# Feature Development Systematic feature development: understand the problem, explore the codebase, design the solution, implement with TDD, verify it works, and review. ## Available skills and subagents The following skills and subagents are available in this repo to delegate work to. Use them instead of doing everything inline — they have specialized instructions and keep your context clean: - **`/tdd`** — Implement changes using Test-Driven Development (Red-Green-Refactor). Delegate implementation tasks to this. - **`/e2e`** — Write and run Playwright E2E tests using TDD. Use for the final wave when the full feature needs end-to-end coverage. - **`code-review` subagent** — Review changed code for quality, security, and architecture compliance. Also verifies the feature works: traces wiring, tests edge cases, and writes tests for gaps. - **`verify` subagent** — Run fmt, typecheck, test, and lint across the monorepo, then fix any issues found. - **`simplify` subagent** — Simplify recently changed code — inline one-off abstractions, remove speculative code, reduce nesting. - **`/record`** — Record architectural decisions or save implementation plans for future reference. --- ## Before anything else: create the pipeline The first thing you do — before reading code, before asking questions, before any exploration — is create a task list for the full pipeline. This is non-negotiable because it keeps you accountable to the process and lets the user see where you are. Crea