implement-feature

Implement approved feature specs through architecture design, coding, testing, and documentation.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill implement-feature-artemiopadilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/ArtemioPadilla/agent-triforce/tree/main/.claude/skills/implement-feature
Command: npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill implement-feature-artemiopadilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • End-to-end feature implementation: from spec to code, tests, and docs
  • Architecture-first approach: design interfaces and plan layers before coding
  • Traceable delivery: maintain documentation and ADRs for decisions

Quick Start

Provide the feature specification and let the skill implement it following the described design, test, and documentation steps.

Frequently Asked Questions about implement-feature

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

FAQPage Schema
How do I implement a feature from a spec end-to-end?

Feature implementation from a spec is automated by reading the specification, designing the architecture, writing code, testing, and generating documentation to deliver the feature completely.

What is the architecture-first approach to software feature implementation?

An architecture-first approach designs interfaces and plans layers before coding, ensuring the feature spec is structurally sound and traceable before test-driven development begins.

How do I use test-driven development to implement an approved feature spec?

Test-driven development is applied during feature implementation by writing tests alongside the code generated from the spec, verifying that all requirements are met before delivery.

Can I generate architecture decision records and documentation automatically from a spec?

Architecture decision records and documentation are generated automatically during implementation to maintain traceable delivery and provide auditable handoffs for the approved spec.

Do I need an approved feature specification before starting automated implementation?

An approved feature specification is required beforehand, because the implementation agent reads the spec directly to design architecture, write tests, and deliver the finalized code.