Skip to content
Back to skills

Implement Feature

ASecurity

Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 28, 2026
ai-agentsrefactoringdocumentation

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add ArtemioPadilla/agent-triforce --skill implement-feature --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement Feature?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement Feature
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/artemiopadilla-implement-feature/badge)](https://www.skillsdirectory.com/skills/artemiopadilla-implement-feature)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: implement-feature
description: >
  Implements a feature from its specification. Reads the spec, designs architecture,
  writes code, tests, and documentation. Use after a feature spec has been approved.
context: fork
agent: forja-dev
---

Implement the feature: $ARGUMENTS

Follow these steps:

**SIGN IN:**
- Run the SIGN IN checklist from your agent file
- Run the Receiving-from-Prometeo checklist to verify the spec handoff
- If significant architecture decisions are needed, create an ADR in `docs/adr/`

**DESIGN:**
1. Define interfaces/contracts first — program to interfaces, not implementations
2. Plan the layer structure: entities → use cases → adapters → frameworks (Clean Architecture)
3. Identify which business logic needs TDD (test-first) vs infrastructure glue (test-after acceptable)

**BUILD (TDD Cycle):**
4. For each piece of business logic:
   a. **Red**: Write a failing test that describes the expected behavior (Arrange-Act-Assert)
   b. **Green**: Write minimal code to make the test pass
   c. **Refactor**: Clean up — extract methods, improve names, remove duplication
   d. Verify each acceptance criterion from the spec has at least one test — if not, write one before proceeding
5. Implement infrastructure/adapters and write integration tests for critical paths
6. Scan for and remove any dead code you introduced or found

**⏸️ TIME OUT — Run Implementation Complete Checklist (DO-CONFIRM):**
7. Run through every item in the Implementation Complete checklist from your agent file
8. Fix any failures BEFORE proceeding

**REFACTORING PASS:**
9. Review all new code for code smells: long methods, feature envy, data clumps, primitive obsession
10. Apply Extract Method, Rename, Move as needed — leave code better than you found it

**⏸️ TIME OUT — Run Pre-Delivery Checklist (DO-CONFIRM):**
11. Run through every item in the Pre-Delivery checklist from your agent file
12. Fix any failures BEFORE proceeding

**SIGN OUT:**
13. Write the Handoff-to-Centinela using the communication checklist
14. Run the SIGN OUT checklist from your agent file

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.