Write code from specifications and design documents in TDD or standard workflows.
npx skills add https://github.com/felipe3dfx/dotfiles --skill sdd-apply-felipe3dfx
Please help me install this Agent Skill. Skill: sdd-apply Source: https://github.com/felipe3dfx/dotfiles/tree/main/skills/sdd-apply Command: npx skills add https://github.com/felipe3dfx/dotfiles --skill sdd-apply-felipe3dfx
This Skill automates the process of writing code to fulfill specific tasks defined in project change specifications, ensuring adherence to design and requirements.
Use the sdd-apply skill to implement tasks 1.1 through 1.3 from the current change.
High-intent search queries and answers about installing and using this skill.
To implement code changes from design specifications, you can automate the process by writing code that directly fulfills tasks defined in project change specs. This ensures adherence to established design documents, project conventions, and requirements.
Yes, test-driven development with spec-driven coding workflows is fully supported. The implementation process adapts to either TDD or standard development methodologies, ensuring code changes follow established project guidelines and tests.
The best way to automate feature implementation from change specs is to invoke an implementation tool that writes code based on provided specifications. It manages artifact updates and tracks progress based on specified modes like engram or openspec.
Yes, you need predefined design documents and change specifications to automate task implementation. The coding process relies on these provided specs to ensure modifications adhere to project conventions and accurately fulfill the defined requirements.
Progress tracking when implementing tasks from specifications works by managing artifact updates based on specified modes like engram or openspec. This ensures the development workflow maintains accurate records of task completion and code modifications.
A limitation when writing code based on provided specifications is that the implementation quality depends entirely on the accuracy of the input design documents. If the change specs lack detail, the automated coding may not fully adhere to project conventions.
dallayCreate a dependency-ordered implementation task checklist in openspec/changes/{change-name}/tasks.md.
dopsonbrValidate implementation work against plan specifications with Codex CLI reviews.
kaptinlinGenerate CLAUDE.md and AGENTS.md guidelines from repository structure and docs.
romiluz13Enforce the red-green-refactor TDD cycle with failing tests before production code.
