Is user confirmation required before task creation?

Yes, the skill mandates a preview and explicit 'yes/no' confirmation before creating any subtasks, even if the user indicates they are in a hurry.

Can it parse subtasks from any file format?

It is optimized for Markdown files, specifically looking for headers, numbered lists, bullet points, and checkboxes within sections like 'Tasks' or 'Implementation'.

How does the skill handle duplicate subtasks?

It uses smart merge logic to check existing subtasks; it will automatically skip exact matches and ask for user confirmation for similar titles.

Does this skill automatically create git branches?

No, this skill focuses strictly on linking design documents and creating task hierarchies; branch creation is handled by separate workflows like flow:start.

Linking Design

Name: Linking Design
Author: NoNameItem

byNoNameItem

Productivity & Workflow

Automates the transition from design to execution by linking documents and generating structured subtasks from design files.

About

This skill streamlines the post-design workflow for developers using the beads task system. It intelligently identifies the relevant design document and parent task, parses implementation steps into subtasks with heuristic logic, and performs a smart merge to avoid duplicates. By enforcing a mandatory preview and confirmation step, it ensures that task hierarchies are accurate and approved before any modifications are made, maintaining high project organization standards without manual data entry.

Key Features

Automated linking of design document paths to task descriptions
Intelligent identification of active in-progress parent tasks
Smart merge logic to prevent duplicate subtask creation
Heuristic subtask extraction from Markdown design files
0 GitHub stars
Mandatory preview and confirmation workflow for data integrity

Use Cases

Managing complex feature rollouts by breaking down design docs into manageable leaf tasks
Syncing task boards with newly finalized technical architecture documents
Converting Requirements or Implementation sections of Markdown files into actionable subtasks

About

Key Features

Automated linking of design document paths to task descriptions
Intelligent identification of active in-progress parent tasks
Smart merge logic to prevent duplicate subtask creation
Heuristic subtask extraction from Markdown design files
0 GitHub stars
Mandatory preview and confirmation workflow for data integrity

Use Cases

Managing complex feature rollouts by breaking down design docs into manageable leaf tasks
Syncing task boards with newly finalized technical architecture documents
Converting Requirements or Implementation sections of Markdown files into actionable subtasks