implement

Translate SDD design specs into production code with progress tracking.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill implement-lleontor705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/implement
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill implement-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing SDD-driven changes requires translating design decisions and specifications into production-ready code with traceable artifacts and progress tracking across the pipeline.

Core Features & Use Cases

  • Translates SDD design decisions and task specifications into working, production-ready code following project conventions.
  • Tracks task completion, updates progress markers, and persists artifacts to the cortex-based knowledge graph and OpenSpec when applicable.
  • Supports the apply phase of the SDD pipeline by coordinating access to spec, design, and tasks and generating a formal apply-progress report.

Quick Start

Invoke the apply-phase workflow to translate tasks into production code and update progress artifacts.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I translate SDD design decisions into production code?

To translate SDD design decisions into production code, invoke the apply-phase workflow to turn task specifications into working code while updating progress artifacts. It enforces strict adherence to design constraints, tests, and persistence rules.

How do I track task completion and progress in a TDD implementation pipeline?

Tracking task completion in a TDD implementation pipeline is handled by updating task marks and persisting artifacts to the cortex-based knowledge graph and OpenSpec. This ensures traceable progress artifacts across the SDD apply phase.

What is the SDD apply pipeline and when do I need it for automation testing?

The SDD apply pipeline is a structured workflow that coordinates access to specs, designs, and tasks to generate production-ready code. You need it for automation testing when translating design decisions requires strict constraint enforcement and formal progress reporting.

Can I use this implementation workflow without existing design references and task assignments?

Using this implementation workflow without existing design references and task assignments is not recommended, as it operates within the SDD apply pipeline by coordinating access to specifications and designs to enforce strict adherence to project constraints.

Does the implementation pipeline enforce strict adherence to tests and persistence rules?

Yes, the implementation pipeline enforces strict adherence to design constraints, tests, and persistence rules. It updates task marks and progress artifacts to ensure code generation follows the defined SDD specifications and project conventions.

What's the best way to generate a formal apply-progress report for task-tracking?

The best way to generate a formal apply-progress report for task-tracking is to invoke the apply-phase workflow. It supports the SDD pipeline by coordinating spec, design, and task access while persisting progress artifacts to the knowledge graph.