Menu
Use when fixing bugs with tdd is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
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.
Basé sur la classification professionnelle SOC
| name | fixing-bugs-with-tdd |
| description | Use when fixing bugs with tdd is required during implementation work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent. |
| license | MIT |
| compatibility | ForgeOS-compatible Agent Skills hosts; no provider-specific model required. |
| metadata | {"author":"forgeos-community","version":"0.2.0","pack":"implementation","kind":"core","status":"candidate"} |
This skill owns one bounded responsibility: fixing bugs with tdd. Its focus is fixing bugs with tdd within implementation lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.
Activate only when the project is in one of these stages: implementation, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.
execution-planacceptance-contractsfilesystem, shellProduce or reference all applicable evidence:
fixing-bugs-with-tdd-decision-tablefixing-bugs-with-tdd-verification-reportfixing-bugs-with-tdd-handoff-envelopeEvidence must identify the current artifact hash, command or method used, result, reviewer identity, timestamp, and limitations.
Produce:
implemented-incrementThe primary artifact must include schema version, provenance, consumed artifact IDs, decisions, evidence references, residual risks, validation state, and invalidation targets. Narrative explanation may accompany the artifact but cannot replace it.
Reviewer: independent-reviewer
Pass only when: All mandatory rules pass, evidence targets the current artifact hash, and no unresolved critical finding applies.
Stop and request a human decision when scope, risk acceptance, irreversible action, cost ceiling, privacy boundary, or product direction is materially ambiguous. When this artifact changes, invalidate only descendants named by the artifact graph; preserve unaffected verified branches.
implemented-increment.contract-validation, independent-review, fixing-bugs-with-tdd-decision-table, fixing-bugs-with-tdd-verification-report, fixing-bugs-with-tdd-handoff-envelope.artifactId, schemaVersion, sha256, producingSkill, producingAgent, consumedArtifacts, decisionIds, evidenceIds, residualRisks, validationState, invalidationTargets, stopCondition.Load at most 8 direct artifacts and reference depth 1. Use stable IDs, hashes, signatures, and deltas instead of repeating full history. Use established domain terminology, state each requirement once, and spend context on decisions, code, tests, or evidence rather than narration.
Load skills/references/core/implementation.md only when this skill needs pack-wide decision tables, evidence patterns, or cross-skill handoff rules.
See contract.json for the machine-readable contract.
Use when choosing system architecture is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Use when decomposing bounded contexts is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Use when defining domain model is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Use when designing api contracts is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Use when designing data migrations is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Use when designing data model is required during architecture work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.