smith-implement

Execute implementation plans by coordinating tasks and recording progress in a vault.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-implement
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-implement
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, auditable harness for executing complete implementation plans by coordinating tasks, tracking workflow state, and recording outcomes in a vault.

Core Features & Use Cases

  • End-to-end plan execution: orchestrates setup, tests, core development, integration, and polish phases with deterministic task ordering.
  • Per-branch workflow tracking and vault logging: creates ephemeral workflow records and logs progress and artifacts for auditability.
  • TDD-oriented execution: encourages tests before code and progressive validation with clear progress reporting.

Quick Start

Describe your implementation plan and run the smith-implement action to execute tasks.

Frequently Asked Questions about smith-implement

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

FAQPage Schema
How do I automate end-to-end implementation plan execution with auditable task tracking?

End-to-end implementation plan execution is automated by coordinating tasks from setup through polish phases into working code artifacts. The workflow orchestrates deterministic task ordering and records progress per-branch in a vault to ensure full traceability and auditability.

What's the best way to enforce test-first development during automated workflow execution?

Test-first development is enforced through a TDD-oriented execution harness that processes tests before core code. Progressive validation runs at each phase, providing clear progress reporting and ensuring setup, integration, and polish tasks follow the correct sequence.

Can I use per-branch workflow tracking and vault logging for stepwise code generation?

Per-branch workflow tracking and vault logging are supported by creating ephemeral workflow records that log progress and artifacts for each task. This ensures stepwise code generation remains fully auditable across setup, tests, development, integration, and polish phases.

How does phase-based execution manage deterministic task ordering for implementation plans?

Phase-based execution manages deterministic task ordering by orchestrating setup, tests, core development, integration, and polish phases sequentially. It coordinates tasks defined by frontmatter metadata and records outcomes to a vault for strict workflow state tracking.

Do I need a ledger integration to track working code artifacts during plan execution?

A ledger integration is not required to track working code artifacts, as core progress is recorded using per-task logging to a vault. Ledger integration is optional, providing an additional layer of outcome recording if your project requires extended auditability.