tashan-development-loop

Align product vision with executable plans through PRD, plan, tests, and code traceability.

5|1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/lemonhall/tashan-development-loop --skill tashan-development-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tashan-development-loop
Source: https://github.com/lemonhall/tashan-development-loop/tree/main/tashan-development-loop
Command: npx skills add https://github.com/lemonhall/tashan-development-loop --skill tashan-development-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined framework to ensure PRD -> plan -> test -> code traceability, preventing documentation drift and rework, ensuring alignment between vision and implementation.

Core Features & Use Cases

  • End-to-end governance: enforces the linkage from PRD to vN plans, tests, and code, keeping artefacts in sync.
  • Gatekeeping & DoD: implements DoD gates, ECN processes, and traceability matrices for auditable delivery.
  • Documentation hygiene: promotes explicit IDs, trace matrices, and upgrade/downgrade workflows to avoid drift across documents.

Quick Start

Start by drafting a PRD, then create a versioned plan (docs/plan/vN-<topic>), align tests and code, and push commits to establish traceable progress.

Frequently Asked Questions about tashan-development-loop

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

FAQPage Schema
How do I maintain traceability between PRD, plans, tests, and code?

To maintain PRD-to-code traceability, align your product vision with executable plans through versioned documents, tests, and code. Enforce traceability matrices and explicit IDs to keep artefacts in sync and prevent documentation drift.

What is a DoD gate in software development and when do I need it?

A DoD gate is a checkpoint enforcing end-to-end validation before delivery. You need it for medium-to-large projects requiring strict documentation, auditable decisions, and traceable progress to prevent rework and ensure alignment.

How to enforce documentation hygiene and prevent documentation drift in git projects?

Prevent documentation drift by enforcing explicit IDs, traceability matrices, and upgrade/downgrade workflows. Keep your PRD, versioned plans, tests, and code in sync through disciplined commits and auditable ECN processes.

Can I use this disciplined execution framework for small agile projects?

This framework is designed for medium-to-large projects requiring strict documentation, versioned plans, and end-to-end validation. Small agile projects may find the DoD gates and ECN workflows too heavy for their scale.

How do I start implementing a traceability matrix for my project plans?

Start implementing a traceability matrix by drafting a PRD, then create a versioned plan like docs/plan/vN-topic. Align tests and code to the plan, and push commits to establish traceable progress and auditable delivery.

Why does my project suffer from documentation drift and rework?

Documentation drift and rework happen when PRD, plans, tests, and code lack enforced traceability. Without gatekeeping mechanisms like DoD gates and traceability matrices, artefacts fall out of sync and vision alignment fails.