Executes predefined SDD tasks with support for multiple metadata backends.
npx skills add https://github.com/kurojs/EnderDots --skill sdd-apply-kurojs
Please help me install this Agent Skill. Skill: sdd-apply Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-apply Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-apply-kurojs
It helps an executor safely implement SDD change tasks by turning orchestrator-assigned specs and designs into correct, reviewable code updates while preserving prior progress.
engram, openspec, hybrid, and none modes to read required artifacts and persist apply progress.size:exception) before writing code.Load the sdd-apply skill as an executor, then implement only the specific tasks assigned for the given change name while updating tasks completion and saving apply-progress according to the selected artifact mode.
High-intent search queries and answers about installing and using this skill.
To implement SDD change tasks safely, load an executor skill that reads existing apply-progress and merges newly completed tasks. This preserves prior completions while applying assigned task slices against provided specifications and design decisions.
The strict TDD cycle for SDD apply-phase execution follows the RED, GREEN, TRIANGULATE, and REFACTOR sequence. When strict mode is enabled, executors must maintain a TDD cycle evidence table to verify each step before proceeding.
Artifact persistence modes determine how required task artifacts are read and apply-progress is saved during SDD implementation. Supported modes include engram, openspec, hybrid, and none, each defining different storage and retrieval strategies for task artifacts.
Executing multiple assigned task slices requires passing the review forecast gate to resolve the delivery path. The executor enforces workload and PR boundary constraints, allowing auto-chain, chained slice, single PR, or size exception decisions before writing code.
If delivery decisions are missing, the apply-phase execution halts at the review forecast gate. The executor requires a resolved delivery path from the orchestrator or user to ensure workload and PR boundary constraints are met before writing any code.
SDD apply-phase execution works without strict TDD requirements by implementing assigned tasks normally using specifications as acceptance criteria. Strict TDD mode is optional and only enforces the RED, GREEN, TRIANGULATE, REFACTOR contract when explicitly enabled.
lleontor705Translate SDD design specs into production code with progress tracking.
45ckVerify implemented code against planning artifacts and generate a deviations report.
oterowebInitialize Spec-Driven Development context by detecting tech stack and bootstrapping persistence modes.
Codename-IncAutomate TDD cycles with failing tests before production code.