coding

Orchestrate the eight-phase spec-tree TDD workflow with mandatory gates.

1|Updated Jan 6, 2026

Search Tags:#workflow #testing #tdd #architecture #phases #spec-tree

Ready to run

npx skills add https://github.com/outcomeeng/claude --skill coding-outcomeeng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spec-tree/skills/coding
Command: npx skills add https://github.com/outcomeeng/claude --skill coding-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a disciplined spec-tree TDD workflow to ensure work items are implemented only after a complete planning and testing cycle.

Core Features & Use Cases

Enforces eight sequential phases with mandatory gates to guarantee quality and traceability.
Maps phases to language-specific actions (Python and TypeScript) to facilitate correct tooling integration.
Prevents ad hoc implementation by requiring structured tests before coding and by enforcing review gates.

Quick Start

Load the methodology once per session, load work item context for each node, and progress through Phases 3–8 with gating until APPROVED.

Frequently Asked Questions about coding

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

FAQPage Schema

How do I enforce structured TDD phases before implementation in my workflow?▼

To enforce structured TDD, you can use a spec-tree workflow that sequences eight phases with mandatory testing and review gates before any coding begins. This prevents ad hoc implementation by requiring formal approvals.

What is the best way to prevent ad hoc implementation during software development?▼

The best way to prevent ad hoc implementation is orchestrating a disciplined spec-tree TDD workflow, which guarantees work items are coded only after completing a full planning cycle and passing mandatory architecture and test gates.

How do I get started with a spec-tree TDD workflow for a new work item?▼

To start a spec-tree TDD workflow, load the methodology once per session, load the context for each work item node, and progress through phases three to eight with mandatory gating until the review is APPROVED.

Does the spec-tree TDD workflow support language-specific tooling for Python and TypeScript?▼

Yes, the spec-tree TDD workflow maps its phases to language-specific actions for Python and TypeScript, facilitating correct tooling integration and ensuring tests align with the target language environment.

Why does my TDD workflow require formal approvals before moving to the next phase?▼

Formal approvals are required to enforce mandatory gating within the TDD workflow, ensuring that each phase satisfies quality and traceability requirements before the project progresses to subsequent implementation stages.