coferlandia-project-manager

Manage project portfolios and Epic planning across GitHub Issues, Projects, and local work-item contracts.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-project-manager-coferlandia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coferlandia-project-manager
Source: https://github.com/coferlandia/coferlandia-skills/tree/main/skills/ops/coferlandia-project-manager
Command: npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-project-manager-coferlandia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Coordinating multiple software projects with AI agents often leads to duplicated task databases, stale status tracking, and unclear handoffs between planning and execution. This Skill provides a single portfolio and project-architecture layer that treats GitHub Issues and Projects as the authoritative work state, eliminating conflicting sources of truth. ## Core Features & Use Cases - Epic Planning and Architecture Gate: Transform rough ideas or requirements into structured Epic contracts with execution strategy selection, and route cross-cutting initiatives through an architecture preflight before execution. - GitHub-Native Portfolio Reporting: Generate portfolio, project, and issue-level reports from GitHub Issues, Projects, and Git state, with local fallback planning under .agent/work-items/ when GitHub is unavailable. - Registry and Projection Management: Maintain a projects.json portfolio registry, run health checks and onboarding diagnostics, and generate disposable Obsidian projections without duplicating operational state. - Use Case: Register five repositories, run pm-portfolio-report.sh to see open, blocked, and in-review Issues across all of them, then plan a new Epic with an explicit execution strategy and hand it to a coding agent or orchestrator. ## Quick Start Ask the agent to onboard the project manager with scripts/pm-onboard.sh, register your repositories, and produce a portfolio report of open and blocked GitHub Issues.

Frequently Asked Questions about coferlandia-project-manager

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

FAQPage Schema
How do I manage multiple GitHub projects from one place?▼

Register each repository with pm-manage-projects.sh add, which records portfolio membership in projects.json. Then run pm-portfolio-report.sh to aggregate open, in-progress, review, and blocked Issues across all managed repositories from GitHub.

How do I plan an Epic before handing work to a coding agent?▼

Use the Epic Planner capability to produce a master contract covering problem statement, scope, acceptance criteria, and execution strategy. The planner records whether Analyst decomposition is needed and whether an architecture preflight gate applies before execution begins.

Does this work without GitHub CLI access?▼

Yes, planning can fall back to local mode where Epic contracts are written under .agent/work-items/ instead of GitHub Issues. GitHub-backed reporting and Project operations still require an authenticated gh CLI with the project token scope.

What are the prerequisites for the project manager scripts?▼

Bash, git, and Python 3.11+ are always required. GitHub-backed operations additionally need the gh CLI authenticated for the managed repositories, plus a token with the project scope for GitHub Projects reads and mutations.

Why should I not keep TODO.md or HISTORY.md files?▼

The skill treats GitHub Issues and Projects as the only authoritative operational state, so legacy TODO/HISTORY files are migration inputs only. Keeping them risks divergent status tracking; migrate them through the Archivist before relying on GitHub-native reporting.

Can the project manager merge branches or push code?▼

No. The skill only inspects repositories and GitHub state; it never creates development branches, merges, or pushes. Delivery workflows own their own Git lifecycle, and worktree cleanup suggestions remain advisory-only.