How do I install the Orchestrating SPEC-First TDD Development skill?

Run npx skillmds add majiayu000/orchestrating-spec-first-tdd-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orchestrating SPEC-First TDD Development safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orchestrating SPEC-First TDD Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orchestrating SPEC-First TDD Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Orchestrating SPEC-First TDD Development?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orchestrating SPEC-First TDD Development by majiayu000

Name: Orchestrating SPEC-First TDD Development
Rating: 4.2 (5 reviews)
Author: majiayu000

Orchestrating SPEC-First TDD Development

Guides agents through SPEC-First TDD workflow with context engineering, TRUST principles, and @TAG traceability. Essential for /alfred:1-plan, /alfred:2-run, /alfred:3-sync commands. Covers EARS requirements, JIT context loading, TDD RED-GREEN-REFACTOR cycle, and TAG chain validation.

majiayu000 ab9786d 2 files · 2.5 KB Updated Sep 9, 2026 567 repo stars

File contents

Alfred Development Guide Skill

Core Workflow: SPEC → TEST → CODE → DOC

No spec, no code. No tests, no implementation.

1. SPEC Phase (`/alfred:1-plan`)

Author detailed specifications first with @SPEC:ID tags
Use EARS format (5 patterns: Ubiquitous, Event-driven, State-driven, Optional, Constraints)
Store in .moai/specs/SPEC-{ID}/spec.md

2. TDD Phase (`/alfred:2-run`)

RED: Write failing tests with @TEST:ID tags
GREEN: Implement minimal code with @CODE:ID tags
REFACTOR: Improve code while maintaining SPEC compliance
Document with @DOC:ID tags

3. SYNC Phase (`/alfred:3-sync`)

Verify @TAG chain integrity (SPEC→TEST→CODE→DOC)
Synchronize documentation with implementation
Generate sync report

Key Principles

Context Engineering: Load only necessary documents at each phase

/alfred:1-plan → product.md, structure.md, tech.md
/alfred:2-run → SPEC-{ID}/spec.md, development-guide.md
/alfred:3-sync → sync-report.md, TAG validation

TRUST 5 Pillars:

T – Test-driven (RED→GREEN→REFACTOR)
R – Readable (clear naming, documentation)
U – Unified (consistent patterns, language)
S – Secured (OWASP compliance, security reviews)
E – Evaluated (metrics, coverage ≥85%)

Common Patterns

Scenario	Action
Write tests first	RED phase: failing tests with @TEST:ID
Implement feature	GREEN phase: minimal code with @CODE:ID
Refactor safely	REFACTOR phase: improve code structure
Track changes	Always use @TAG system in code + docs
Validate completion	`/alfred:3-sync` verifies all links

---name: orchestrating-spec-first-tdd-developmentdescription: Guides agents through SPEC-First TDD workflow with context engineering, TRUST principles, and @TAG traceability. Essential for /alfred:1-plan, /alfred:2-run, /alfred:3-sync commands. Covers EARS requirements, JIT context loading, TDD RED-GREEN-REFACTOR cycle, and TAG chain validation.--- # Alfred Development Guide Skill ## Core Workflow: SPEC → TEST → CODE → DOC **No spec, no code. No tests, no implementation.** ### 1. SPEC Phase (`/alfred:1-plan`) - Author detailed specifications first with `@SPEC:ID` tags - Use EARS format (5 patterns: Ubiquitous, Event-driven, State-driven, Optional, Constraints) - Store in `.moai/specs/SPEC-{ID}/spec.md` ### 2. TDD Phase (`/alfred:2-run`) - **RED**: Write failing tests with `@TEST:ID` tags - **GREEN**: Implement minimal code with `@CODE:ID` tags - **REFACTOR**: Improve code while maintaining SPEC compliance - Document with `@DOC:ID` tags ### 3. SYNC Phase (`/alfred:3-sync`) - Verify @TAG chain integrity (SPEC→TEST→CODE→DOC) - Synchronize documentation with implementation - Generate sync report ## Key Principles **Context Engineering**: Load only necessary documents at each phase - `/alfred:1-plan` → product.md, structure.md, tech.md - `/alfred:2-run` → SPEC-{ID}/spec.md, development-guide.md - `/alfred:3-sync` → sync-report.md, TAG validation **TRUST 5 Pillars**: 1. **T** – Test-driven (RED→GREEN→REFACTOR) 2. **R** – Readable (clear naming, documentation) 3. **U** – Unified (consistent patterns, language) 4. **S** – Secured (OWASP compliance, security reviews) 5. **E** – Evaluated (metrics, coverage ≥85%) ## Common Patterns | Scenario | Action | |----------|--------| | Write tests first | RED phase: failing tests with @TEST:ID | | Implement feature | GREEN phase: minimal code with @CODE:ID | | Refactor safely | REFACTOR phase: improve code structure | | Track changes | Always use @TAG system in code + docs | | Validate completion | `/alfred:3-sync` verifies all links |

Frequently asked questions