implement

Automate batch implementations with requirement tracing and constitution compliance.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill implement-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.ghcp-appmod/skills/implement
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill implement-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end batch implementation tasks with strict requirement tracing and constitution compliance, returning results without updating checkpoints or tasks.md.

Core Features & Use Cases

  • Batch-based execution with requirement tracing from spec to plans and checkpoints
  • Source-anchored implementation (rewrite mode) that preserves behavioral parity with source references
  • Conformance to constitution principles including testing discipline, observability, and traceability across tasks

Quick Start

Initiate a batch implementation by providing the batch context and task IDs to execute.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate batch implementation with requirement tracing across multiple tasks?

Batch implementation with requirement tracing is automated by providing batch context and task IDs, coordinating checkpoints and plans to ensure strict traceability to REQ-XXX identifiers and constitution compliance. It returns a structured batch result report without updating checkpoints.

What is source-anchored implementation and how does it maintain behavioral parity?

Source-anchored implementation is a rewrite mode that preserves behavioral parity with source references during batch execution. It ensures code rewrites conform to original source behavior while enforcing testing discipline and observability across coordinated tasks.

How do I enforce testing discipline and constitution compliance during end-to-end batch implementations?

Testing discipline and constitution compliance are enforced automatically during batch implementations by applying constitution principles to every task. The workflow coordinates checkpoints, plans, and rewrites to guarantee observability and traceability across the entire batch.

Can I coordinate multiple tasks with checkpoints and plans in a single batch execution?

Yes, you can coordinate multiple tasks in a single batch execution by providing batch.task_ids. The workflow applies checkpoints and plans to each task, ensuring dependencies are enforced and results are traced back to spec references.

Does batch implementation update checkpoints or tasks.md after execution?

No, batch implementation does not update checkpoints or tasks.md after execution. It returns a structured batch result report containing the traced implementation outcomes, leaving checkpoint management to external processes.

When do I need requirement tracing for batch task execution?

Requirement tracing for batch task execution is needed when multiple tasks must coordinate with strict spec and plan references. It ensures every implementation step maps to REQ-XXX identifiers, enforcing dependencies and testing discipline across the batch workflow.