| 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.
CRITICAL RULES
- You MUST follow EVERY step in order. No step can be skipped, even if it seems trivial or unnecessary.
- You MUST NOT create a PR until ALL prior steps are completed. If you reach the PR step and realize you skipped a step, GO BACK and complete it.
- Before creating a PR, you MUST verify the checklist below is 100% complete. Print the checklist with checkmarks. If any step is unchecked, you cannot proceed.
- If the user rejected a step (e.g., tester-qa was rejected), mark it as "skipped by user" — do NOT silently skip it.
- Complete one ticket fully before starting the next. Never parallelize tickets.
Mandatory Checklist
You MUST maintain this checklist throughout the implementation. Print it before creating the PR to verify completeness:
- [ ] 1. TDD — Write failing tests first - test-writer agent
- [ ] 2. IMPLEMENTATION — Implement the feature - hexagonal agent
- [ ] 3. TEST SUITE — Run full test suite, all green
- [ ] 4. CODE REVIEW — Run code-reviewer skill, fix any critical issues - code-reviewer agent
- [ ] 5. CODE SIMPLIFIER — Run code-simplifier skill - code-simplifier agent
- [ ] 6. LINTER — Run linter skill (ruff for Python, eslint+prettier for TypeScript)
- [ ] 7. RUN all unit tests
- [ ] 8. SONARQUBE — Run sonar-scanner, verify 0 new issues - sonarfix skill
- [ ] 9. TRIVY — Run trivy fs scan, verify 0 vulnerabilities - trivyfix skill
- [ ] 10. TESTER-QA — Rebuild Docker, run tester-qa agent for manual verification - tester-qa agent
- [ ] 11. DOCUMENTATION — Update or create documentation if needed - documentation-writer agent```
**Before step 10 (PR), verify ALL boxes 1-10 are checked.** If any is missing:
- STOP
- Print the checklist showing which steps are incomplete
- Complete the missing steps
- Only then proceed to PR
## Development Workflow Details
### 1. Test-First Development
- **test-writer** — Write failing tests following TDD (Red-Green-Refactor cycle)
### 2. Implementation
- **hexagonal** agent — Implement using hexagonal/clean architecture patterns appropriate to the project
### 3. Full Test Suite
- Run the FULL test suite (not just new tests): `uv run pytest tests/ -x -q` (Python), `npx vitest run` (TypeScript)
- ALL tests must pass with 0 failures
### 4. Code Review
- **code-reviewer** skill — Review the implementation for bugs, security issues, and best practices
- Fix any critical or high-severity issues found
- Commit fixes
### 5. Code Simplifier
- **code-simplifier** skill — Refactor to reduce complexity while maintaining functionality
- Run tests again after simplification
### 6. Linter
- **linter** skill — Run ruff (Python) and/or eslint+prettier (TypeScript)
- Fix all linting issues before proceeding
### 7. Unit Tests
- Run all unit tests again to ensure no regressions
### 8. SonarQube
- **sonarfix** skill — Run SonarQube analysis
- Verify 0 new issues on the branch
### 9. Trivy
- **trivyfix** skill — Run Trivy vulnerability scan
- Verify 0 new vulnerabilities
### 10. Tester-QA
- **tester-qa** agent — Rebuild Docker images, restart stack, perform manual testing
- Verify all acceptance criteria are met end-to-end
- Try to find bugs that automated tests missed by trying edge cases and error scenarios
- If bugs found: iterate back to step 5, fix, then re-run steps 6-12
### 11. Documentation
- **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 only if changes are internal refactors with no user-facing impact
- If sonarfix or trivyfix find issues, iterate back to implementation to fix, then re-run the relevant check
- When chaining multiple tickets, be EXTRA vigilant about completing all steps — this is when steps get skipped
