tdd-docs-init

Scaffold missing docs from codebase analysis into docs/.

4|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-docs-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-docs-init
Source: https://github.com/CurtisThe/three-pillars-plugin/tree/main/skills/tdd-docs-init
Command: npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-docs-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds architecture.md, product_roadmap.md, and known_issues.md in docs/ from codebase analysis, ensuring the docs reflect the current state of the project and the TDD pipeline needs.

Core Features & Use Cases

  • Automatically creates architecture.md, product_roadmap.md, and known_issues.md when missing, based on repository insights.
  • Aligns scaffolds with docs/vision.md, surfacing recommendations if vision is missing and guiding the user to /tdd-setup.
  • Preserves existing documentation unless regeneration is explicitly requested, enabling safe scaffolding.

Quick Start

Run /tdd-docs-init to scaffold architecture.md, product_roadmap.md, and known_issues.md in docs/.

Frequently Asked Questions about tdd-docs-init

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

FAQPage Schema
How do I scaffold architecture and roadmap docs for my codebase?

You can generate architecture documentation from your codebase by running an initialization command that analyzes the repository and scaffolds architecture.md, product_roadmap.md, and known_issues.md in the docs folder.

Will scaffolding project documentation overwrite my existing markdown files?

Scaffolding project documentation is non-destructive, meaning it preserves existing markdown files unless you explicitly request a regeneration, ensuring your current architecture and roadmap docs remain safe.

Do I need a vision document to generate architecture and roadmap markdown files?

You do not need a vision document to generate architecture and roadmap files, but if docs/vision.md is missing, the scaffolding process will surface recommendations guiding you to set up your project vision.

What is the best way to align new architecture documentation with a project vision?

The best way to align architecture documentation with a project vision is to derive the scaffolded content directly from repository analysis, ensuring generated docs reflect the current codebase state and TDD pipeline needs.

Can I use this scaffolding tool for any repository with a docs folder?

Yes, you can use this scaffolding tool for any repository with a docs folder, as it analyzes the codebase to generate missing architecture and roadmap markdown files while maintaining consistency with existing project insights.