publish-tasks

Publish uncompleted OpenSpec tasks as grouped GitHub issues.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/daodaoedu/daodao --skill publish-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-tasks
Source: https://github.com/daodaoedu/daodao/tree/main/.claude/skills/publish-tasks
Command: npx skills add https://github.com/daodaoedu/daodao --skill publish-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual and error-prone process of converting uncompleted OpenSpec task checklists into actionable GitHub issues so remote agents can pick them up and implement work automatically.

Core Features & Use Cases

  • Select and validate change: Choose an OpenSpec change, auto-select when unambiguous, and validate target repository access via gh.
  • Context-rich issue generation: Read tasks.md, proposal.md, design.md, and specs to build self-contained issue bodies that include Why, Tasks, Technical Context, and Acceptance Criteria.
  • Grouping, sizing, and safeguards: Group related checkbox tasks into 2–8 hour issues per section, ensure an 'auto' label exists, preview issues for user confirmation, and never publish already-completed tasks; use Traditional Chinese for issue content to match project conventions.

Quick Start

Publish uncompleted tasks from the OpenSpec change named add-reactions to GitHub repository daodaoedu/daodao-server.

Frequently Asked Questions about publish-tasks

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

FAQPage Schema
How do I publish OpenSpec tasks to GitHub issues for remote agent automation?

To publish OpenSpec tasks to GitHub issues, the Skill parses uncompleted checklist items from tasks.md, groups them into 2–8 hour issues, and creates them in a target GitHub repository. It validates repository access via gh and ensures an 'auto' label exists before publishing.

How does this Skill group OpenSpec checklist tasks before creating GitHub issues?

It groups unchecked tasks by section into manageable 2–8 hour GitHub issues. This sizing prevents remote agents from being overwhelmed, ensuring each issue contains related tasks with sufficient context from proposal.md and design.md to be self-contained.

Do I need the GitHub CLI (gh) installed to automate task publishing from OpenSpec?

Yes, the GitHub CLI (gh) is required to validate target repository access and create issues. The Skill uses gh to verify permissions and ensure the 'auto' label exists in the repository before publishing any uncompleted OpenSpec tasks.

Can I preview GitHub issues before they are created from OpenSpec changes?

Yes, you can preview issues before creation. The Skill composes self-contained Traditional Chinese issue bodies including Why, Tasks, Technical Context, and Acceptance Criteria, then presents them for user confirmation before pushing to the GitHub repository.

What context is included in GitHub issues generated from OpenSpec tasks?

GitHub issues generated from OpenSpec tasks include Why, Tasks, Technical Context, and Acceptance Criteria. The Skill reads tasks.md, proposal.md, design.md, and specs/ files to build self-contained Traditional Chinese issue bodies for remote agent implementation.

Will this tool publish already completed OpenSpec tasks to GitHub?

No, it never publishes already-completed tasks. The Skill specifically parses unchecked tasks from the OpenSpec tasks.md file, ensuring only uncompleted work is grouped, sized, and pushed to GitHub for remote agent automation.