sdd-tasks

Break SDD change proposals into phase-ordered implementation tasks.

2|Updated Jul 29, 2025

Search Tags:#architecture #task planning #sdd #test planning #pr workflow #dependency ordering #artifact persistence

Ready to run

npx skills add https://github.com/kurojs/EnderDots --skill sdd-tasks-kurojs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-tasks
Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-tasks-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a software design document into a concrete, dependency-ordered task breakdown so implementation can start quickly and safely.

Core Features & Use Cases

Breaks SDD changes into actionable phases (foundation, core implementation, integration/wiring, and testing).
Produces a standardized tasks artifact for the chosen persistence mode (engram, openspec, hybrid, or none).
Optimizes for review readiness by forecasting review workload against a 400-line budget and recommending chained PRs when needed.

Quick Start

Ask the orchestrator to generate implementation tasks for a specific change name and storage mode so this skill returns a fully structured tasks breakdown.

Frequently Asked Questions about sdd-tasks

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

FAQPage Schema

How do I break a software design document into implementable tasks?▼

To break a software design document into implementable tasks, you need a structured task planning process that reads proposal and design artifacts, then generates a dependency-ordered breakdown across foundation, core implementation, integration, and testing phases.

What is the best way to structure implementation phases for an SDD change proposal?▼

The best way to structure implementation phases for an SDD change proposal is to divide the work into foundation, core implementation, integration or wiring, and testing phases, ensuring dependency ordering so implementation can start safely and quickly.

How do I plan pull requests when a software design change exceeds the review line budget?▼

To plan pull requests when a software design change exceeds the review budget, you should forecast the review workload against a 400-line limit and recommend chained PRs to keep the workload manageable and review-ready.

Can I persist task planning artifacts in an openspec directory instead of a custom sdd path?▼

Yes, you can persist task planning artifacts in an openspec directory by using the openspec delivery strategy, which stores the generated tasks file under openspec/changes/{change-name}/tasks.md instead of the default sdd path.

Do I need a specific artifact store format to generate a task breakdown from a design proposal?▼

You need to read proposal, spec, and design documents from an agreed artifact store to generate a task breakdown, producing a standardized tasks artifact using engram, openspec, hybrid, or none persistence modes.

When should I not use a single PR workflow for a large software architecture change?▼

You should not use a single PR workflow for a large software architecture change when the review workload forecast exceeds the 400-line budget, requiring chained PRs with a chain-strategy guard contract to manage the review process.