project-manager-init

Generate PROJECT_MANAGE.md with GitHub Project binding and field mappings.

16|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/hojinzs/github-symphony --skill project-manager-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-manager-init
Source: https://github.com/hojinzs/github-symphony/tree/main/.claude/skills/project-manager-init
Command: npx skills add https://github.com/hojinzs/github-symphony --skill project-manager-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial setup of project management conventions for a repository, providing a single source of truth for board binding and field mappings.

Core Features & Use Cases

  • Generates PROJECT_MANAGE.md at repo root containing project rules, board binding, and field IDs.
  • Guides pre-flight checks for authentication and permissions and proposes or detects project fields.
  • Serves as the canonical input for subsequent project-manager:* commands.
  • Use Case: New repositories or teams adopting GitHub Projects can run this to quickly establish consistent governance.

Quick Start

Run the project-manager-init skill in the target repository to generate PROJECT_MANAGE.md and begin configuring GitHub Project bindings.

Frequently Asked Questions about project-manager-init

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

FAQPage Schema
How do I initialize project management conventions for a GitHub repository?

To initialize project management conventions, run this skill in your target repository to generate a `PROJECT_MANAGE.md` file containing GitHub Project board binding configurations and field ID mappings.

What is a PROJECT_MANAGE.md file used for in GitHub repository automation?

A `PROJECT_MANAGE.md` file stores project rules, board binding settings, and field IDs using YAML frontmatter, serving as the canonical configuration input for subsequent project-manager automation commands.

Do I need gh CLI authentication to set up GitHub Project board binding?

Yes, you need gh CLI authentication with project scope permission to set up GitHub Project board binding, as the initialization process guides through pre-flight authentication checks and project board selection.

Can I configure GitHub Project field mappings automatically when adopting project governance?

Yes, you can configure GitHub Project field mappings automatically, as the initialization process detects existing project fields or proposes new ones to establish consistent governance for new repository teams.

What's the best way to establish consistent project governance across new GitHub repositories?

The best way to establish consistent governance is automating repository-level project setup by generating a canonical `PROJECT_MANAGE.md` with predefined board bindings and field mappings for team-wide adoption.

Why does project board selection fail during repository project management initialization?

Project board selection fails during initialization when gh CLI authentication is missing or lacks the required project scope permission, preventing the retrieval of available GitHub Projects for binding.