skills.rest
realworldtech
realworldtechOFFICIAL
Explore all skills by this author →
Website𝕏@realworldtechGitHub

implement

Track spec-driven implementation tasks with per-requirement verification and test integration.

3|Updated Jan 26, 2026
Search Tags:#workflow#verification#spec#drift#implement#sub-agent#tracker
One-click install
npx skills add https://github.com/realworldtech/claude-implement-skill --skill implement-realworldtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/realworldtech/claude-implement-skill/tree/main/skills/implement
Command: npx skills add https://github.com/realworldtech/claude-implement-skill --skill implement-realworldtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Implement skill helps teams maintain a consistent, auditable workflow for turning specifications into working code, guarding against drift by anchoring work to the source spec and a persistent tracker.

Core Features & Use Cases

  • Provides a robust process to evolve specs into tracked tasks, with per-requirement verification and test integration.
  • Maintains a persistent implementation tracker (.impl-tracker-<spec-name>.md) to bridge context and source documents.
  • Enables safe delegation to sub-agents for discrete requirements and ensures verification before completion.

Quick Start

  1. Start a new implementation with /implement <path-to-spec.md> to begin tracking and planning.
  2. Use /implement status [name], /implement continue [name], and /implement verify [name] to progress.
  3. Run tests after each sub-task and update the tracker accordingly.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I prevent spec drift during code implementation?▼

To prevent spec drift during implementation, maintain a persistent tracker file bridging context and source documents, enabling per-requirement verification and formal completion only after tests pass.

How do I maintain traceability between software requirements and working code?▼

Traceability between requirements and code is maintained by anchoring implementation work to a persistent tracker file (.impl-tracker-<spec-name>.md), evolving specs into discrete tracked tasks with documented verification workflows.

Can I delegate discrete spec requirements to sub-agents?▼

You can delegate discrete requirements to sub-agents for safe task execution, ensuring the sub-agent verifies completion by running tests before updating the implementation tracker.

What is the best way to verify per-requirement implementation against a spec?▼

The best way to verify per-requirement implementation is running tests after each sub-task and updating the tracker accordingly, applying rigorous drift control to ensure formal completion.

How do I start spec-driven implementation using a tracker file?▼

Start spec-driven implementation by providing a path to your spec markdown file, which initiates tracking and planning, then use status and continue commands to progress through verification.

Related Skills

Explore More Software Engineering Skills→
sipherxyzsipherxyz
1

implementation-plan

Generate implementation plans with task breakdowns, file manifests, and dependencies.

Official
Intermediate
EduardoJVNEduardoJVN

sdd-verify

Validate code implementations against project specifications and design documents.

Community
Advanced
ZESCODEZESCODE

ZES-executing-plans

Execute structured development plans with task-based verification checkpoints.

Community
Advanced
dougsillarsdougsillars

braingrid-cli

Transform unstructured ideas into detailed requirements and AI-executable tasks via CLI.

Community
Intermediate