skills.rest
so-ota-biz
so-ota-bizCOMMUNITY
Explore all skills by this author →
GitHub

issue-driven-start

Initialize issue-driven development from GitHub, Notion, or local spec files.

Updated Aug 27, 2026
Search Tags:#planning#templates#github#notion#backlog#design-doc#issue-driven
One-click install
npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill issue-driven-start
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-driven-start
Source: https://github.com/so-ota-biz/ai-agent-orchestration-settings/tree/main/.agent/skills/issue_driven_start
Command: npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill issue-driven-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and initiate issue-driven development from multiple starting points (GitHub issues, backlog tickets, Notion pages, or local spec files) to standardize project setup.

Core Features & Use Cases

  • Centralizes inputs from issues/backlogs/Notion/local specs
  • Loads and applies startup templates to define save locations and design/test workflows
  • Guides early design and test artifact creation before design approval
  • Use Case: starting a new feature from a GitHub issue, a Notion task, or a local Markdown spec triggers a consistent plan and artifacts.

Quick Start

Use the issue_driven_start skill by passing an issue URL or local spec path to begin the workflow and initialize the template-driven plan.

Frequently Asked Questions about issue-driven-start

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

FAQPage Schema
How do I standardize project setup from a GitHub issue or Notion page?▼

To standardize issue-driven development, this centralizes inputs from GitHub issues, Notion pages, and local specs to load startup templates, define artifact save locations, and enforce consistent design and test workflows.

What is the best way to initiate issue-driven development from multiple backlog sources?▼

Initiating issue-driven development from multiple sources involves passing a backlog ticket URL or local spec path to trigger a consistent plan, load authoritative templates, and clarify early artifact creation rules.

Can I use local Markdown spec files to generate design docs for issue-driven development?▼

Yes, you can use local Markdown spec files as a starting point. The workflow guides early design doc and test artifact creation before design approval by applying defined templates to your local spec.

Does issue-driven project initialization work with both GitHub issues and Notion tasks?▼

Issue-driven project initialization works with both GitHub issues and Notion tasks. It centralizes these inputs to provide defined handoff conventions and template-driven plans before design approval.

How do I define where design and test artifacts are saved when starting a new feature?▼

To define where design and test artifacts are saved when starting a new feature, this loads authoritative startup templates that specify save locations and clarify creation rules before design approval.

Related Skills

Explore More Software Engineering Skills→
AppsVortexAppsVortex
31

arn-code-pick-issue

Filter GitHub, Jira, or local backlog issues and route the selected one to Arness planning workflows.

Official
Intermediate
Maru1301Maru1301

speckit-plan

Execute a standardized plan template workflow to generate design artifacts.

Community
Advanced
flowgladflowglad
2

flowglad-subscriptions

Manage subscription lifecycles via cancelSubscription, adjustSubscription, uncancelSubscription, and reload.

Official
Advanced
luzhenqianluzhenqian
149

openspec-ff-change

Generate all OpenSpec artifacts for a specified change with dependency-aware sequencing.

Community
Advanced