Search

PythonReactSEOPDF
GitHub Skill

aico-backend-implement

Execute backend implementation with TDD (Test-Driven Development). Write failing test first, then implement, verify each step. Use this skill when: - User asks to "implement this backend task", "implement backend" - Have an implementation plan ready and need to execute it - Executing steps from /backend.plan output - User says "start coding backend", "write backend code" - User asks to "use TDD", "write test first", "test-driven" for backend code - Fixing backend bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/backend/tasks/ (use /backend.tasks first if not exists) - MUST read constraints.md before writing any code. Flow: Check Task File → Read Constraints → TDD Cycle (RED→GREEN→REFACTOR) → Verify Each → Run All Tests → Update Task Status → Notify PM

yellinzero☆ 1 Repository stars0 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

Features and purpose

Execute backend implementation with TDD (Test-Driven Development). Write failing test first, then implement, verify each step. Use this skill when: - User asks to "implement this backend task", "implement backend" - Have an implementation plan ready and need to execute it - Executing steps from /backend.plan output - User says "start coding backend", "write backend code" - User asks to "use TDD", "write test first", "test-driven" for backend code - Fixing backend bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/backend/tasks/ (use /backend.tasks first if not exists) - MUST read constraints.md before writing any code. Flow: Check Task File → Read Constraints → TDD Cycle (RED→GREEN→REFACTOR) → Verify Each → Run All Tests → Update Task Status → Notify PM

Quick start

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

Guides ↗

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-21
Index updated
2026-03-03
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!