speckit-taskstoissues

Convert design-artifact tasks into dependency-ordered GitHub issues.

Updated Jun 8, 2025
One-click install
npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-taskstoissues-cicero78m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/cicero78M/Cicero_Web/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-taskstoissues-cicero78m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered design-artifact tasks into actionable, dependency-ordered GitHub issues to streamline feature delivery.

Core Features & Use Cases

  • Translates tasks into linked GitHub issues and organizes them by their dependency order.
  • Uses available design artifacts to derive scope, enabling consistent traceability from design to implementation.
  • Supports dependency-aware issue creation workflows and downstream planning.

Quick Start

Convert your existing design-artifact tasks into a prioritized set of GitHub issues.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert design artifacts into GitHub issues with dependencies?

To convert design artifacts into GitHub issues, this Skill reads scattered design-artifact tasks and derives a dependency-ordered list of actionable GitHub issues. It ensures consistent traceability from design to implementation by organizing the linked issues by their required execution order.

What is the best way to automate creating linked GitHub issues from feature development tasks?

Automating linked GitHub issue creation is handled by translating design-artifact tasks into dependency-aware issues. This approach enables downstream planning workflows by generating multiple related issues with explicit dependencies rather than manual entry.

Does this issue generation workflow validate the remote repository scope before creating issues?

Yes, repository scope validation is performed to ensure issues are created only in the correct remote repository. This prevents accidental task decomposition and issue generation in unrelated project repositories during the workflow.

How do I organize scattered project-management tasks into a dependency-ordered list for GitHub?

Organizing scattered project-management tasks into a dependency-ordered list involves reading available design-artifact sources. The Skill derives scope from these artifacts and generates GitHub issues explicitly ordered by their task dependencies.

Can I use spec-kit design artifacts to drive task decomposition for multiple related issues?

Yes, spec-kit design artifacts can drive task decomposition for multiple related issues. The Skill applies to feature development workflows where design artifacts are read and translated into a set of linked, dependency-ordered GitHub issues.