AgentSkillsCN

tdd-task-architect

将用户故事分解为符合 TDD 要求的技术任务的流程。在第 4 节（首席开发工程师）中使用此流程，以确保架构单元严格遵循“红—绿—重构”这一开发顺序。

SKILL.md
--- frontmatter
name: tdd-task-architect
description: Process for decomposing user stories into TDD-compliant technical tasks. Use during Session 4 (Lead Developer) to ensure architectural units follow the Red-Green-Refactor sequence.

TDD Task Architect

Ensures implementation plans are testable and follow project-standard TDD cycles.

Core Workflow

  1. •Unit Decomposition: Break the story into tiny, testable logic units (Services, Models).
  2. •Task Sequencing: Order tasks following the Red-Green-Refactor pattern.
  3. •Reference Patterns: Consult tdd-patterns.md for concrete examples and command-line verification steps.

Principles

  • •Small Units: Tasks must be small enough for one subagent execution.
  • •Isolation: Design services to be testable without the full scene tree.
  • •Traceability: Every task must trace back to the Active User Story.

Artefacts to Update (when creating tasks)

  • •Add task entries to ./docs/todo/master_todo.md under the related story ID and include which files will be changed (e.g., src/services/MatchService.gd, tests/unit/test_match_service.gd).
  • •Create unit tests in ./tests/unit/ alongside task implementation and add them to the task checklist.
  • •Commit test skeletons and task docs before implementing code changes to make the TDD flow explicit.