skills.rest
AstralDeep
AstralDeepOFFICIAL
Explore all skills by this author →
GitHub

speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues.

Updated Aug 23, 2026
Search Tags:#workflow-orchestration#project-management#github-issues#task-automation#dependency-resolution#design-artifacts
One-click install
npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-taskstoissues-astraldeep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/AstralDeep/astralprojection-flutter/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-taskstoissues-astraldeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered design tasks and artifacts into actionable, dependency-ordered GitHub issues, enabling teams to plan and track work from design artifacts.

Core Features & Use Cases

  • Automates conversion of design artifacts into GitHub issues aligned by task dependencies.
  • Enforces dependency order so work proceeds in correct sequence.
  • Integrates with .specify/ project structure to source tasks from design docs.

Quick Start

From the repo root, run the speckit taskstoissues workflow to convert design tasks into GitHub issues ordered by dependencies.

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 dependency-ordered GitHub issues?▼

To convert design artifacts into dependency-ordered GitHub issues, apply this Skill to a repository containing a .specify/ structure and a GitHub remote URL. It automatically sources tasks from design docs and publishes them in the correct sequence.

What is the best way to automate task creation from design docs to GitHub issues?▼

Automating task creation from design docs to GitHub issues is best handled by converting the design artifacts within a .specify/ structure. This enforces dependency resolution so work proceeds in the correct sequence on your GitHub remote.

Do I need a compatible MCP server to publish GitHub issues from design tasks?▼

Yes, you need a compatible MCP server to publish GitHub issues from design tasks. The workflow requires both a GitHub remote URL and the server to push the dependency-ordered issues directly to your target repository.

Can I use .specify/ structure to enforce dependency resolution for feature work?▼

Yes, you can use a .specify/ structure to enforce dependency resolution for feature work. The Skill reads task dependencies from design artifacts within this directory and outputs issues aligned by those required sequences.

Why does workflow orchestration require a .specify/ directory for task automation?▼

Workflow orchestration requires a .specify/ directory for task automation because it serves as the source location for design tasks. Without this structure, the workflow cannot extract the artifacts needed to generate dependency-ordered issues.

Related Skills

Explore More Software Engineering Skills→
AhmedHassaan-7OSAhmedHassaan-7OS

speckit-taskstoissues

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

Community
Intermediate
kinncjkinncj
23

gh-projects

Automates GitHub Project V2 board management by adding issues and updating fields.

Community
Intermediate
augenticaugentic
1

status

Display Specify change lifecycle, artifact completion, and task progress.

Official
Intermediate
jeremyaryjeremyary
7

pm-exports

Generate Jira JSON, Linear CSV, and GitHub Projects Markdown export templates.

Community
Intermediate