← Browse

@davepoon/implement-feature

A

Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.

skillclaude

Install

agr install @davepoon/implement-feature --target claude

Writes 1 file into .claude/skills/, pinned to git-843bf4b5.

  • .claude/skills/implement-feature/SKILL.md

Document


name: implement-feature category: workflow-orchestration description: Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.

Implement Feature

Implements a feature from its specification using the Forja (Dev) agent.

When to Use This Skill

  • A feature spec has been approved and is ready for implementation
  • You need architecture design, code, and tests for a defined feature
  • Translating product requirements into working software

What This Skill Does

  1. Runs the SIGN IN checklist and verifies the spec handoff
  2. Designs architecture (creates ADR if needed)
  3. Defines interfaces/contracts, then implements in src/
  4. Writes tests in tests/ (unit + integration)
  5. Runs the Implementation Complete checklist (TIME OUT 1)
  6. Runs the Pre-Delivery checklist (TIME OUT 2)
  7. Prepares structured handoff to QA agent
  8. Runs the SIGN OUT checklist

How to Use

Basic Usage

/implement-feature webhook-event-system

With Spec Reference

/implement-feature docs/specs/webhook-event-system.md

Example

User: /implement-feature user-authentication

Output:

  • Implementation in src/ with all acceptance criteria met
  • Tests in tests/ covering critical paths
  • ADR if significant architecture decisions were made
  • Handoff notes for QA: files changed, how to test, known limitations

Tips

  • Ensure the feature spec exists before running this skill
  • The agent creates an ADR for any significant architecture decisions
  • Two TIME OUT checkpoints ensure both correctness and delivery cleanliness

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-843bf4b5799a2026-07-31