implementing-stories

Test-driven development automation enforces architectural constraints by validating code against six context files, including tech-stack.md and source-tree.md. It guides the AI through the Red-Green-Refactor cycle, ensuring code compliance before implementation.

The best way to automate code generation for user stories without technical debt is using a TDD workflow with strict constraint validation. This Skill validates against architecture constraints, anti-patterns, and coding standards at every step to ensure compliance.

Constraint validation during story implementation works by checking generated code against six context files covering technology stack, source tree, dependencies, coding standards, architecture constraints, and anti-patterns at every step of the TDD cycle.

Yes, you can use this for TDD code generation with specific anti-patterns to avoid. The Skill enforces rules from a dedicated anti-patterns context file throughout the Red-Green-Refactor cycle, ensuring generated code avoids your defined architectural violations.

Yes, you need to provide context files to use this TDD automation. The Skill requires six context files covering technology stack, source tree, dependencies, coding standards, architecture constraints, and anti-patterns to enforce guardrails and validate implementation.

The story implementation process prompts you for decisions during code generation to resolve ambiguities. Instead of guessing, the Skill uses explicit questions to clarify unclear choices, ensuring the final TDD code matches your intent and architectural constraints.