Transform change proposals into implementation-ready technical design documents.
npx skills add https://github.com/kurojs/EnderDots --skill sdd-design-kurojs
Please help me install this Agent Skill. Skill: sdd-design Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-design Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-design-kurojs
It turns a proposed change into a clear, actionable technical design that explains architecture decisions, data flow, and required file changes before implementation begins.
design.md artifact capturing HOW the change will be implemented from the proposal and codebase patterns.openspec/changes/{change-name}/design.md depending on artifact store mode.Use the orchestrator workflow to provide the change name and artifact store mode so this skill can read the proposal/spec, inspect the impacted codebase, and persist the resulting architecture design.
High-intent search queries and answers about installing and using this skill.
To convert a change proposal into a technical architecture design, the skill reads your proposal or spec artifacts, inspects the codebase patterns, and generates an implementation-ready design file detailing data flow, file changes, interfaces, and testing strategy.
A technical design document should include architecture decisions with rationale, data flow mapping, required file changes, interface contracts, and a defined testing strategy to guide implementation from the initial change proposal.
You document architecture decisions and rationale by generating a design artifact that captures concrete choices, alternatives considered, interface definitions, and testing strategy based on the codebase review and proposal specifications.
Yes, you can persist the technical design artifact by configuring the artifact store mode, which allows saving the resulting architecture blueprint under the sdd directory or the openspec changes path.
Yes, the technical design approach requires reading the relevant codebase patterns and proposal specifications to accurately map the data flow and determine the necessary file changes for the implementation blueprint.
The best way to plan a testing strategy during technical design is to generate a comprehensive design artifact that explicitly defines the testing approach alongside interface contracts and data flow before implementation begins.
StrocsGenerate a design.md documenting architecture decisions and data flow for codebase changes.
josemartinrodriguezmortaloniGenerate technical design documents for software changes from proposals and specifications.
yukikmDocument technical architecture decisions, diagrams, and data models.
dallayGenerate technical design documents for proposed code changes.