github-project-tasks

Create and audit GitHub issues and Project board items for Stack-and-Flow workflows.

23|4|Updated May 7, 2025
One-click install
npx skills add https://github.com/Stack-and-Flow/design-system --skill github-project-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-project-tasks
Source: https://github.com/Stack-and-Flow/design-system/tree/main/.atl/skills/github-project-tasks
Command: npx skills add https://github.com/Stack-and-Flow/design-system --skill github-project-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the manual overhead of creating, moving, validating, and closing GitHub issues and GitHub Projects tasks by enforcing the Stack-and-Flow canonical workflow and board field consistency.

Core Features & Use Cases

  • CREATE tasks correctly: generates GitHub issues using the single source of truth template, adds them to the Stack-and-Flow Project board, and sets Status, Team, and Category using the canonical field/option IDs.
  • START WORK safely: assigns the issue to the contributor, ensures the Project item exists, and moves the card to In progress while recording branch and worktree intent before implementation starts.
  • END WORK with evidence: posts completion/validation evidence and only moves the Project item to Done when the PR is merged or an explicit maintainer/user approval is provided.
  • AUDIT existing items: inspects Project items to detect malformed titles/bodies, missing reference sections, missing phases/assignees, and missing closure evidence for Done items.

Quick Start

Use this skill in CREATE, START WORK, END WORK, or AUDIT mode to manage Stack-and-Flow GitHub issue and Project board tasks according to the provided board IDs and the canonical issue body template in references.

Frequently Asked Questions about github-project-tasks

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

FAQPage Schema
How do I automate GitHub issue creation and Project board status updates?

GitHub issue creation and Project board status updates are automated by generating issues with a canonical body template, adding them to the board, and setting Status, Team, and Category using deterministic field IDs.

What is the best way to validate GitHub Project tasks before moving them to Done?

Validating GitHub Project tasks before moving them to Done requires confirming the pull request is merged or receiving explicit maintainer approval, ensuring completion evidence is posted and board field consistency is enforced.

How do I audit GitHub Project board items for missing fields or malformed issues?

Auditing GitHub Project board items inspects existing tasks to detect malformed titles, missing reference sections, missing assignees, and missing closure evidence for items marked as Done.

Can I record branch and worktree plans when starting work on a GitHub issue?

Recording branch and worktree plans when starting work on a GitHub issue assigns the contributor, ensures the Project item exists, and moves the card to In progress before implementation begins.

Does GitHub workflow automation enforce canonical board fields for task lifecycles?

GitHub workflow automation enforces canonical board fields by applying deterministic field/option IDs and following a single source of truth template across CREATE, START WORK, END WORK, and AUDIT task phases.

Why does my GitHub Project board item fail validation during an audit?

A GitHub Project board item fails validation during an audit if it has malformed titles, missing reference sections, missing phases or assignees, or lacks closure evidence for Done items.