Verified:GitHub

implementing-stories

Automate user story implementation with a strict TDD workflow and architectural constraints.

Updated Aug 2, 2026

Search Tags:#tdd #code generation #test-driven development #architecture enforcement #story implementation #constraint validation

Ready to run

npx skills add https://github.com/bankielewicz/DevForgeAI --skill implementing-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementing-stories
Source: https://github.com/bankielewicz/DevForgeAI/tree/main/.claude/skills/implementing-stories
Command: npx skills add https://github.com/bankielewicz/DevForgeAI --skill implementing-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the implementation of user stories using Test-Driven Development (TDD) while strictly enforcing architectural constraints defined in six context files, thereby preventing technical debt accumulation.

Core Features & Use Cases

TDD Workflow: Guides the AI through the Red-Green-Refactor cycle, writing tests before implementation.
Constraint Enforcement: Validates against tech-stack.md, source-tree.md, and other context files at every step.
Ambiguity Resolution: Uses AskUserQuestion to resolve any unclear decisions, ensuring explicit choices are made.
Use Case: Transform a user story like "As a user, I want to add items to my cart" into fully tested, compliant code that adheres to the project's defined architecture and technology stack.

Quick Start

Use the implementing stories skill to implement the user story for adding items to the shopping cart.

Frequently Asked Questions about implementing-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement user stories with test-driven development while enforcing architecture constraints?▼

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.

What is the best way to automate code generation for user stories without accumulating technical debt?▼

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.

How does constraint validation work during story implementation?▼

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.

Can I use this for TDD code generation if my project has specific anti-patterns to avoid?▼

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.

Do I need to provide context files to use test-driven development automation?▼

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.

Why does the story implementation process prompt me for decisions during code generation?▼

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.