Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

tdd-implementation-loop

Étoiles3

Forks1

Mis à jour6 mai 2026 à 14:23

Use when implementing behavior from an approved plan with test-first or regression-test-first development.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

artreimus

artreimus/software-factory-starter

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	tdd-implementation-loop
description	Use when implementing behavior from an approved plan with test-first or regression-test-first development.

TDD Implementation Loop

Workflow

Read AGENTS.md, the active plan, and the relevant spec.
Identify the smallest behavior that can be proven by a test.
Add or update the failing test first when practical.
Implement the minimal code needed to pass.
Run the focused test.
Repeat until the planned behavior is covered.
Run the full required validation before handoff.

Rules

Keep tests tied to user-visible behavior or durable service contracts.
Prefer deterministic tests over broad snapshot or prompt-output assertions.
When test-first is not practical, explain why and add the strongest regression coverage available.
Update docs/specs if implementation changes current behavior or accepted scope.

Output

Return changed files, tests added, validation commands, and any behavior that remains untested.

Plus depuis ce dépôt

même dépôt

mcp-tool-policy-review

artreimus/software-factory-starter

Use when adding, changing, or reviewing MCP servers, agent tools, provider integrations, credentials, scopes, or tool approval behavior.

2026-05-063

spec-to-plan

artreimus/software-factory-starter

Use when converting a product spec, use case, or PRD into a concrete implementation plan before code changes.

2026-05-063

agentic-code-review

artreimus/software-factory-starter

Use to review a diff against repository contracts, specs, docs, tests, and architecture boundaries.

2026-05-063

factory-retrospective

artreimus/software-factory-starter

Use after incidents, regressions, repeated review findings, or completed features to convert lessons into durable factory improvements.

2026-05-063

plan-before-code

artreimus/software-factory-starter

Use when a task requires meaningful implementation. Research the repo, inspect docs/specs, and create a concrete plan before editing code.

2026-05-063

subagent-supervisor

artreimus/software-factory-starter

Use when splitting complex work into independent subagent tasks with clear ownership, evidence, and integration responsibilities.

2026-05-063

name	tdd-implementation-loop
description	Use when implementing behavior from an approved plan with test-first or regression-test-first development.

TDD Implementation Loop

Workflow

Read AGENTS.md, the active plan, and the relevant spec.
Identify the smallest behavior that can be proven by a test.
Add or update the failing test first when practical.
Implement the minimal code needed to pass.
Run the focused test.
Repeat until the planned behavior is covered.
Run the full required validation before handoff.

Rules

Keep tests tied to user-visible behavior or durable service contracts.
Prefer deterministic tests over broad snapshot or prompt-output assertions.
When test-first is not practical, explain why and add the strongest regression coverage available.
Update docs/specs if implementation changes current behavior or accepted scope.

Output

Return changed files, tests added, validation commands, and any behavior that remains untested.