specd-implement

Implement SpecD change tasks across workspaces with guardrails and hooks.

12|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/specd-sdd/SpecD --skill specd-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specd-implement
Source: https://github.com/specd-sdd/SpecD/tree/main/.gemini/skills/specd-implement
Command: npx skills add https://github.com/specd-sdd/SpecD --skill specd-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to translate change designs into concrete code by following the change artifacts, executing tasks, and updating the task checklist in real time.

Core Features & Use Cases

  • End-to-end implementation: reads status, design, and artifacts to implement tasks for a SpecD change while honoring guardrails and dependencies.
  • Hook-driven workflow: explicitly runs pre and post hooks during transitions to exercise project context rules and validations.
  • Audit-ready progress: marks each task as done as it is completed and triggers exit hooks, ensuring traceability.

Quick Start

Follow the change design and task artifacts to implement the change, marking each task as done as you complete it.

Frequently Asked Questions about specd-implement

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

FAQPage Schema
How do I automate end-to-end code implementation from a change design?

Automating end-to-end code implementation involves reading context, design, and artifacts to produce task-complete code deltas. It enforces readOnly guardrails, applies dependency-aware task sequencing, and runs pre and post hooks for validation.

What is dependency-aware task sequencing in code generation workflows?

Dependency-aware task sequencing orders code generation tasks based on their interdependencies, ensuring prerequisite tasks complete before dependent ones. It applies graph analysis to maintain structural integrity across multiple workspaces.

Can I use readOnly guardrails to protect existing code during automated changes?

Yes, readOnly guardrails protect existing code by preventing unauthorized modifications to files outside the change scope. They enforce safe, auditable writes and trigger validation steps through pre and post hooks.

How do pre and post hooks work during code implementation transitions?

Pre and post hooks execute project context rules and validations before and after task transitions during code implementation. They ensure traceability by running explicitly during state changes and marking tasks as done.

What's the best way to maintain audit-ready progress when implementing changes across multiple workspaces?

The best way to maintain audit-ready progress is by marking each task as done upon completion and triggering exit hooks. This ensures traceability across multiple workspaces while enforcing strict guardrails and processing artifacts.

Why does automated code generation require graph analysis and artifact processing?

Automated code generation requires graph analysis and artifact processing to satisfy strict guardrails and ensure safe, auditable writes. These steps validate dependency relationships and process change artifacts to produce accurate code deltas.