tddlisted

Use when the user wants a technical design document (TDD) for any work item — epic, story, bug, or spike — at docs/work/{work-id}/tdd.md, in skeleton or full mode. Pass a work item ID (CHK01, or a Linear/Jira/GitHub key like JIRA-123). Resolves the source system and writes at whatever level the ID names — a story gets its own tdd.md beside its parent epic's, not nested inside it. Cite solution.md — do not re-narrate architecture. Triggers on "tdd CHK01", "write the technical design for JIRA-123", "design the epic", "how should we build this story". For reviewing an existing tdd.md, use docs-review instead. Do NOT use for test-driven development — writing a failing test first, red/green/refactor, or any test-authoring task is implement. Do NOT use to write the breakdown itself — stories, tasks, or sub-tasks (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).
carinyaparc/skills · ★ 2 · Code & Development · score 77

Install: claude install-skill carinyaparc/skills

# Technical design document You are a Software Architect writing a technical design document at `docs/work/{work-id}/tdd.md`, for whatever work item the argument names — an epic, a story, a bug, or a spike. Read [work-item-resolution.md](../tasks/references/work-item-resolution.md) **first** — it resolves the source system and canonical ID before you touch the backlog or the tracker. If the ID resolves to a story, bug, or spike, also read its parent epic's context (backlog row or tracker epic, and its `tdd.md` if one exists) — cite it by ID rather than re-narrating it. This skill writes design documents. It is **not** test-driven development — requests to write a failing test first, or to drive code through red/green/ refactor, belong to **implement**. ## Conventions Read [delivery-conventions.md](../tasks/references/delivery-conventions.md) when resolving `{work-id}` or checking artefact boundaries. ## Artefact `docs/work/{work-id}/tdd.md` — implementation specification for one work item (skeleton or full), keyed by *that item's own* canonical ID. A story's TDD sits at `docs/work/{story-id}/tdd.md`, alongside its parent epic's folder, not inside it. ## Path resolution Default: `docs/work/{work-id}/tdd.md`. User-named paths under `docs/work/` override. Repos written before this skill was renamed from `design` hold the same artefact at `docs/work/{work-id}/design.md`. When that file exists and `tdd.md` does not, say so, `git mv` it to `tdd.md`, and update it in place