spec-planlisted

# Spec Plan Write a plan so clear that any engineer can follow it. Let the human tear it apart through annotation cycles until it's right. Then create structured tasks. This skill does not write code. ## Artifacts ``` docs/specs/YYYY-MM-DD-<feature-name>/ ├── design.md ← From spec-brainstorm (approved) └── plan.json ← This skill's output ``` The plan starts as a markdown draft for human annotation, then gets converted to structured plan.json when approved. ### plan.json Schema ```json { "feature": "user-authentication", "spec": "docs/specs/2026-03-08-user-auth/design.md", "goal": "Add email/password authentication with session management", "phases": [ { "id": "P1", "name": "Domain Model", "tasks": [ { "id": "T1", "name": "Implement UserEntity with validation", "depends_on": [], "inputs": [ "User schema from design.md", "Validation rules (email format, password strength)" ], "description": "Create UserEntity with email and password fields. Implement validation using a Result type. Password must be hashed, never stored plaintext.", "files": { "create": ["src/entities/user.ts", "tests/entities/user.test.ts"], "modify": [] }, "validation": { "tests": [ "rejects empty email", "rejects invalid email format", "rejects weak password", "