skills.rest
CoreStack-Engg
CoreStack-EnggOFFICIAL
Explore all skills by this author →
GitHub

tdd-writing

Generate TDD documents with API contracts, data models, ADRs, and implementation plans.

Updated Mar 13, 2026
Search Tags:#tdd#architecture#documentation#adr#data-models#api-contracts
One-click install
npx skills add https://github.com/CoreStack-Engg/claude-plugins --skill tdd-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-writing
Source: https://github.com/CoreStack-Engg/claude-plugins/tree/main/plugins/architecture/skills/tdd-writing
Command: npx skills add https://github.com/CoreStack-Engg/claude-plugins --skill tdd-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD Writing eliminates ambiguity in technical design by generating comprehensive documentation that includes API contracts, data models, ADRs, and implementation guidance.

Core Features & Use Cases

  • Create API contracts with exact request/response shapes for new features.
  • Document data models, migrations, and indexes to align data architects and engineers.
  • Capture Architecture Decision Records (ADRs) and non-functional requirements for traceability.
  • Enable consistent, review-ready TDDs for handoffs and audits.

Quick Start

Draft a complete TDD package for a feature, including architecture overview, API contracts, data models, ADRs, and an implementation plan.

Frequently Asked Questions about tdd-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a technical design document and when do I need to write one?▼

A technical design document (TDD) eliminates ambiguity in feature design by capturing API contracts, data models, and architecture decisions. You need a TDD during architecture reviews, feature design sessions, or team handoffs to ensure engineering alignment.

How do I write an Architecture Decision Record for a new feature?▼

To write an Architecture Decision Record (ADR), capture the architectural choices and non-functional requirements for traceability. Structured TDD templates document the context, decision, and consequences to align data architects and engineers during reviews.

How do I document API contracts and data models for engineering handoffs?▼

Document API contracts by defining exact request and response shapes, and outline data models including migrations and indexes. Generating comprehensive TDD packages ensures consistent, review-ready documentation that satisfies handoffs and audits between teams.

Does this TDD writing approach work for capturing non-functional requirements?▼

Yes, TDD writing captures non-functional requirements alongside ADRs for traceability. By applying structured templates to feature design sessions, it documents system constraints and architecture decisions to align teams during technical reviews.

What is the best way to structure implementation plans and data migrations in a TDD?▼

The best way to structure implementation plans in a TDD is using structured templates that map data migrations, indexes, and API contracts. This comprehensive documentation approach ensures data architects and engineers stay aligned on feature delivery.

Related Skills

Explore More Software Engineering Skills→
jasonku09jasonku09
10

start-project

Interview users to define project scope, MVP, and core components.

Community
Intermediate
RaNDoM6913RaNDoM6913
1

new-migration

Scaffold paired up/down database migration files with tool detection.

Community
Advanced
Y2138Y2138

fill-api

Implement missing API request functions from design docs and TODO markers.

Community
Intermediate
martimramosmartimramos
1

forge-docs

Generate MkDocs documentation structures and templates for material-theme sites.

Community
Basic