implement

Implement approved atomic specs and generate implementation evidence.

Updated Mar 23, 2026

Search Tags:#workflow #spec-driven #evidence #traceability #software #implement #atomic-spec

Ready to run

npx skills add https://github.com/mattphanm/Codex-Agentic --skill implement-mattphanm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/implement
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill implement-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing code changes based on approved atomic specs, ensuring traceability and escalation when gaps are discovered.

Core Features & Use Cases

Executes one atomic spec at a time and collects evidence
Escalates when spec gaps are discovered to resolve before deployment
Integrates with spec manifests and trace context to maintain alignment

Quick Start

Provide the spec group identifier to begin the implementation process and follow the atomic specs in order.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I implement approved atomic specs with traceable tasks?▼

To implement atomic specs with traceability, provide a spec group identifier to automate the execution process. The system reads spec manifests, loads trace context, and applies changes one atomic spec at a time while collecting implementation evidence.

What happens when gaps are discovered during spec-driven implementation?▼

When spec gaps are discovered during spec-driven implementation, the system escalates the issue to resolve it before deployment. This prevents incomplete requirements from proceeding and maintains alignment with the spec manifest.

How do I manage session checkpoints in a spec-driven workflow?▼

To manage session checkpoints in a spec-driven workflow, the implementation process records progress against atomic specs automatically. It updates statuses and maintains trace context to ensure work can be resumed or audited accurately.

Do I need an approved spec manifest to start implementation?▼

Yes, an approved spec manifest is required to start implementation. The workflow relies on spec manifests to load trace context and execute atomic specs in order, ensuring changes align with approved requirements before deployment.

What is the best way to execute atomic specs in software projects?▼

The best way to execute atomic specs in software projects is through a spec-driven workflow that processes one spec at a time. This approach records implementation evidence and ensures traceability across all approved changes.

Why does spec-driven implementation require recording evidence?▼

Spec-driven implementation requires recording evidence to maintain traceability between the approved specs and the final code changes. This evidence ensures that session checkpoints and requirement updates are verifiable during deployment.