amoa-kanban-management

Manage GitHub Projects V2 kanban boards with GraphQL mutations.

13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-kanban-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amoa-kanban-management
Source: https://github.com/Emasoft/ai-maestro-orchestrator-agent/tree/main/skills/amoa-kanban-management
Command: npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-kanban-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manage and automate GitHub Projects V2 kanban workflows while preventing accidental data loss and permission errors during board, column, and item operations.

Core Features & Use Cases

  • Safe Column Management: Add columns without losing existing option IDs by preserving option metadata and using helper scripts.
  • Item Movement & Sync: Move items between columns, create project items from issues, and reconcile label-to-column status with sync routines.
  • Operational Guards: Pre-flight OAuth scope validation, checks for auto-closed issues when moving to Done, and clear error reporting for GraphQL mutations.
  • Use Case: Onboard a new repository by creating a Projects V2 board, adding the standard 8-column system, and syncing issue labels to board status.

Quick Start

Verify gh CLI project scopes are present and move issue #42 on project 42 into the AI Review column while ensuring the pre-flight check passes.

Frequently Asked Questions about amoa-kanban-management

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

FAQPage Schema
How do I automate GitHub Projects V2 kanban board setup without losing existing column data?

Automate GitHub Projects V2 kanban board setup safely by using GraphQL mutations and helper scripts that preserve existing option IDs. This prevents accidental data loss when adding new columns to your repository or organization workflows.

Why do my GraphQL mutations fail when moving items on GitHub Projects V2 boards?

GraphQL mutations fail when moving items due to missing OAuth scopes. Validate pre-flight OAuth project and read:project scopes using gh CLI to ensure permissions are present before executing board operations.

Can I sync GitHub issue labels to kanban board columns automatically?

Sync GitHub issue labels to kanban board columns automatically using label-to-column synchronization routines. Reconcile status across issues and Projects V2 boards to keep project tracking consistent.

How to move issues to Done on GitHub Projects V2 without auto-closing errors?

Move issues to Done on GitHub Projects V2 safely by applying pre-flight operational guards. Check for auto-closed issues and validate permissions before moving items to prevent errors during status transitions.

Does gh CLI support creating GitHub Projects V2 boards with a standard 8-column system?

Yes, gh CLI supports creating GitHub Projects V2 boards with a standard 8-column system. Use GraphQL mutations to onboard new repositories by generating boards and adding the required columns safely.

What are the limitations of automating GitHub Projects V2 kanban board management?

Limitations include requiring gh CLI authentication with project and read:project scopes and reliance on GraphQL mutations. Option IDs must be preserved using helper scripts to prevent data loss during column modifications.