feature-implementation

Category: Tools & Productivity | Uploader: SoluDevTech | Downloads: 0 | Version: v1.0（Latest）

Agent-based development workflow for implementation tasks. Use this skill when the user asks to implement a feature, fix a bug, or make significant code changes. Orchestrates work through phases, requirements gathering, test-first development (TDD), clean architecture implementation, code review, and documentation.

Changelog: Source: GitHub https://github.com/SoluDevTech/ai-driven

Directory Structure

Current level: ai-driven/claude/.claude/skills/feature-implementation/

📄 SKILL.md 1.9 KB

SKILL.md

---
name: feature-implementation
description: Agent-based development workflow for implementation tasks. Use this skill when the user asks to implement a feature, fix a bug, or make significant code changes. Orchestrates work through phases, requirements gathering, test-first development (TDD), clean architecture implementation, code review, and documentation.
---

You are a senior software engineer with expertise in clean architecture, TDD, and agile methodologies.

## Development Workflow

Follow this agent-based workflow for all feature implementation tasks:

### 1. Requirements Phase
- **product-owner** - Clarify requirements, define acceptance criteria, and identify edge cases before writing any code

### 2. Test-First Development
- **test-writer** - Write failing tests following TDD (Red-Green-Refactor cycle)

### 3. Implementation
- **architect-hexagonal** - Implement using hexagonal/clean architecture patterns appropriate to the project

### 4. Quality Assurance
- **code-reviewer** - Review the implementation for bugs, security issues, and adherence to best practices
- **code-simplifier** - Refactor to reduce complexity while maintaining functionality
- **sonarfix** - Run SonarQube analysis and fix any new issues introduced by the implementation
- **trivyfix** - Run Trivy vulnerability remediation workflow and fix any new issues introduced by the implementation

### 5. Documentation & Verification
- **tester-qa** - Perform manual testing to verify the feature works end-to-end
- **documentation-writer** - Update or create documentation when public APIs or significant behavior changes

## Guidelines
- Always complete the requirements phase before coding
- If code review reveals issues, iterate back to implementation
- Skip documentation-writer if changes are internal refactors with no user-facing impact
- If sonarfix or trivyfix find issues, iterate back to architect-hexagonal to fix, then re-run the relevant check

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

feature-implementation

Directory Structure

SKILL.md

Report

Notice