RsDT

Generate requirement-spec.md, design.md, and tasks.md for feature workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blackjiro/dotfiles --skill rsdt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: RsDT
Source: https://github.com/blackjiro/dotfiles/tree/main/dot_claude/skills/RsDT
Command: npx skills add https://github.com/blackjiro/dotfiles --skill rsdt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RsDT provides a structured workflow to plan features, fix bugs with formal specifications, and decompose work into clear, testable tasks.

Core Features & Use Cases

  • 3-file generation: Create requirement-spec.md, design.md, and tasks.md under RsDT/<feature_name>/ with Japanese content.
  • Guided review: Integrates with rsdt-spec-reviewer to validate drafts before implementation.
  • TDD-driven workflow: Emphasizes writing tests first and incremental implementation, then archiving artifacts.

Quick Start

Create a new RsDT feature by naming it <feature_name>, then generate 3 Japanese documents at RsDT/<feature_name>/ and run the mandatory draft review before proceeding with implementation.

Frequently Asked Questions about RsDT

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

FAQPage Schema
What is specification-driven development and how does it structure feature planning?

Specification-driven development structures feature planning by generating formal requirement-spec, design, and tasks documents to guide implementation. It ensures traceability by decomposing work into clear, testable tasks before coding begins.

How do I plan a feature using requirement-spec, design, and tasks documents?

You plan a feature by naming it and generating three markdown files under a dedicated feature directory. This workflow mandates a draft review of the requirement-spec, design, and tasks before proceeding with implementation.

Can I integrate TDD workflows with formal requirement and design documents?

Yes, this specification-driven approach integrates TDD workflows by emphasizing tests written first alongside incremental implementation. The structured tasks document bridges the design and the test-driven development cycle.

What is the best way to ensure traceability when decomposing software features into tasks?

The best way to ensure traceability is using a specification-driven workflow that archives requirement-spec, design, and tasks documents together. This review-led cycle maintains formal reference artifacts for future feature context.

Do I need a reviewer to validate specification drafts before implementation?

Yes, a guided draft review is mandatory to validate the specification, design, and tasks documents before implementation begins. This review-led step ensures the formal artifacts are accurate and testable.