🎯

feature-development-workflow

🎯Skill

from thapaliyabikendra/ai-artifacts

VibeIndex|
What it does

feature-development-workflow skill from thapaliyabikendra/ai-artifacts

πŸ“¦

Part of

thapaliyabikendra/ai-artifacts(26 items)

feature-development-workflow

Installation

git cloneClone repository
git clone https://github.com/thapaliyabikendra/ai-artifacts.git
npxRun with npx
npx github:thapaliyabikendra/ai-artifacts install .
Install ScriptRun install script
curl -sSL https://raw.githubusercontent.com/thapaliyabikendra/ai-artifacts/main/scripts/install.sh | bash -s -- /path/to/project
npxRun with npx
npx github:thapaliyabikendra/ai-artifacts update
npxRun with npx
npx github:thapaliyabikendra/ai-artifacts uninstall
πŸ“– Extracted from docs: thapaliyabikendra/ai-artifacts
1Installs
4
-
Last UpdatedJan 23, 2026

Skill Details

SKILL.md

"Orchestrate end-to-end feature development from requirements through implementation, testing, and review. Use when: (1) planning feature development stages, (2) coordinating multi-agent feature workflows, (3) understanding SDLC phases for new features."

Overview

# Feature Development Workflow

For complete feature implementation, use the /add-feature command.

Quick Reference

| Command | Time | Use Case |

|---------|------|----------|

| /add-feature "" --minimal | ~2 min | Simple CRUD, no docs |

| /add-feature "" --fast | ~2.5 min | Skip BA, requirements clear |

| /add-feature "" | ~3 min | Standard (progressive handoff) |

| /add-feature "" --full-review | ~4.5 min | With code + security review |

Dependency Chain (Signal-Based)

```

BA(entity+perms) ─┬──→ [Architect + QA-Data] ──→ [Developer + QA-Tests]

🟒 ENTITY_READY β”‚ 🟒 CONTRACTS_READY (parallel implementation)

β”‚

BA(reqs+rules) β”€β”€β”€β”˜ (continues in background, non-blocking)

```

Signal Protocol: Agents emit signals (🟒 ENTITY_READY, 🟒 CONTRACTS_READY) to trigger dependent agents immediately.

Agent Roles

| Stage | Agent | Trigger | Output |

|-------|-------|---------|--------|

| Analyze | business-analyst | Start | Entity definition, permissions, requirements |

| Design | backend-architect | 🟒 ENTITY_READY | Technical design, interface contracts |

| Test Data | qa-engineer | 🟒 ENTITY_READY | TestData.cs, Seeder.cs (parallel with Architect) |

| Implement | abp-developer | 🟒 CONTRACTS_READY | Domain, Application, EF Core layers |

| Tests | qa-engineer | 🟒 CONTRACTS_READY | Unit tests (parallel with Developer) |

| Review | abp-code-reviewer | Phase 2 complete | Review report (optional) |

| Security | security-engineer | Phase 2 complete | Security audit (optional) |

Parallelism Optimizations

  • Phase 1b: Architect + QA-Data run in parallel (on ENTITY_READY)
  • Phase 2: Developer + QA-Tests run in parallel (on CONTRACTS_READY)
  • BA secondary outputs: Non-blocking (requirements.md, business-rules.md)
  • Skipped by default: ANALYSIS.md, impact-analysis.md (use --impact flag)

Full Documentation

See .claude/commands/feature/add-feature.md for complete workflow documentation.