sdd-tasks

Convert software design documents into ordered implementation task breakdowns.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-tasks-zmynxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-tasks
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-tasks-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of turning software design decisions and specifications into structured implementation plans that developers can execute consistently.

Core Features & Use Cases

  • Task Breakdown Generation: Converts SDD proposals, specs, and designs into ordered implementation tasks with dependencies and verification steps.
  • Delivery Planning Support: Estimates review workload, identifies PR splitting needs, and prepares change execution strategies.
  • Use Case: Help an engineering team transform a completed feature design into a detailed tasks.md artifact ready for implementation.

Quick Start

Use the sdd-tasks skill to create an implementation task breakdown for the current software change based on its proposal, specification, and design documents.

Frequently Asked Questions about sdd-tasks

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

FAQPage Schema
How do I convert a software design document into an implementation task breakdown?

Converting software design documents into implementation task breakdowns involves processing completed specs to generate ordered tasks with dependency sequencing, testing considerations, and delivery planning constraints for developers.

What is spec-driven development task planning and when do I need it?

Spec-driven development task planning is the process of turning software specifications into structured implementation plans. You need it when phased planning, dependency ordering, and review workload forecasting are required for consistent development execution.

How do I estimate review workload and PR splitting needs for a feature design?

Estimating review workload and PR splitting needs involves analyzing the generated implementation task breakdown to identify delivery planning constraints and prepare change execution strategies for the engineering team.

Does this workflow support generating a tasks.md artifact from a completed feature proposal?

Yes, this workflow supports generating a tasks.md artifact from a completed feature proposal. It transforms the proposal, specification, and design documents into a detailed artifact ready for implementation execution.

What are the limitations of automating task breakdown generation from software specifications?

A limitation of automating task breakdown generation is that it strictly requires completed software design documents and specifications as input; without finalized design decisions, it cannot produce accurate implementation sequencing or delivery planning.