role-developer

Guide developers through phased workflows, TDD, and systematic debugging.

9|2|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ilandahan/AID --skill role-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-developer
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/role-developer
Command: npx skills add https://github.com/ilandahan/AID --skill role-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The role of a developer in AI.D is to bridge requirements and robust implementation by applying structure, TDD, and disciplined debugging. This Skill helps teams codify a repeatable workflow for implementation, testing, and review to reduce guesswork and rework.

Core Features & Use Cases

  • Role clarity: provides guidance for developers on translating requirements into technical designs, code, tests, and reviews.
  • Phase-driven workflow: aligns discovery, PRD, tech spec, development, and QA with defined outputs.
  • TDD and debugging discipline: follows RED-GREEN-REFACTOR and root-cause analysis to ensure quality and traceability.
  • Defense-in-depth: validates data and operations at multiple layers to prevent regressions and security issues.
  • Async testing and code quality: promotes pattern-based testing, proper error handling, and maintainable architecture.

Quick Start

  • Provide a brief summary of a feature you want to build, describe its interfaces, write a failing test, implement the minimal code to pass, and refactor while preserving tests.

Frequently Asked Questions about role-developer

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

FAQPage Schema
How do I translate requirements into robust, testable software?

Translate requirements into testable software by following a phase-driven workflow spanning Discovery, PRD, tech spec, development, and QA, applying TDD practices and systematic debugging to ensure traceability and reduce rework.

What is the best way to implement TDD and debugging discipline in my workflow?

Implement TDD and debugging discipline by following the RED-GREEN-REFACTOR cycle and conducting root-cause analysis, ensuring your code remains maintainable while preserving passing tests throughout the development phases.

How does defense-in-depth prevent regressions and security issues during development?

Defense-in-depth prevents regressions and security issues by validating data and operations at multiple architectural layers, ensuring systematic error handling and robust protection against edge cases during implementation.

Can I use bash scripts to automate my phase-driven development workflow?

Yes, you can use bash scripts to automate and enforce your phase-driven development workflow, leveraging standardized prompts and references to align discovery, PRD, tech spec, development, and QA outputs.

What's the best way to structure async testing and code review for new features?

Structure async testing and code review by applying pattern-based testing, proper error handling, and documentation-driven design, ensuring multi-layer validation and maintainable architecture across your team's outputs.