create-card

Convert agile card requests into GitHub Issues with titles, bodies, and labels.

2|Updated May 2, 2026
One-click install
npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill create-card-andrecini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-card
Source: https://github.com/andrecini/dotnet-squad-copilot-agent/tree/main/.claude/skills/create-card
Command: npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill create-card-andrecini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of turning agile card ideas (feature, bug, tech debt, spike) into correctly structured GitHub Issues.

Core Features & Use Cases

  • Issue creation from card type: Generates an issue title, a template-filled body, and the correct label for Feature (feat), Bug (fix), Tech Debt (chore), or Spike (spike).
  • Validation before publishing: Prompts you for missing card type, title, or required template sections (including Given/When/Then acceptance criteria where applicable).
  • GitHub API with safe fallback: Attempts to create the Issue via GitHub API, and if it fails, outputs the fully formatted content for manual creation.

Quick Start

Ask the agent to create a Feature card issue with a title and all details needed to fill every template section, including at least one Given/When/Then acceptance criterion.

Frequently Asked Questions about create-card

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

FAQPage Schema
How do I create GitHub Issues from agile card specs during sprint planning?

You can create GitHub Issues from agile card specs by providing a card type and title to automatically generate a template-filled issue body with the correct label. The workflow validates required sections like Given/When/Then acceptance criteria before publishing.

Can I generate GitHub Issue templates for bugs and tech debt automatically?

Yes, GitHub Issue templates for Feature, Bug, Tech Debt, and Spike cards are generated automatically by selecting the appropriate card type. The system applies the correct feat, fix, chore, or spike label and fills the corresponding template sections from your provided context.

What happens when the GitHub API fails during issue creation?

When the GitHub API fails during issue creation, the system provides a complete manual fallback by outputting the fully formatted issue content. This allows you to copy and manually publish the structured agile card without losing the generated template data.

How do I add acceptance criteria to GitHub Issues for backlog refinement?

To add acceptance criteria to GitHub Issues, provide at least one Given/When/Then statement when requesting issue creation. The system validates that these acceptance criteria sections are present in the agile card spec before generating the final GitHub Issue.

Do I need to manually assign labels like feat or fix when creating GitHub Issues?

No, you do not need to manually assign labels because the system limits labels to feat, fix, chore, or spike based on the explicit card type provided. The correct label is applied automatically when the GitHub Issue is generated from the card spec.