agentsclimarketplace
Sign in

Pce memory project manager

Skill CAPHTECH/pce-memory/.claude/skills/pce-memory-project-manager

Manage CAPHTECH/pce-memory GitHub issue, milestone, and Project #18 workflow using the repo-owned config and scripts. Use when asked to organize milestones, assign issues, maintain the kanban or roadmap, or verify project drift.From its SKILL.md

Install
npx -y skills add CAPHTECH/pce-memory --skill pce-memory-project-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

pce-memory Project Manager

Manage CAPHTECH/pce-memory issue planning through repo-owned automation.

Use This Skill For

  • creating or updating milestones for Project #18
  • assigning issues to the configured milestone waves
  • syncing Project #18 fields from repo config
  • verifying drift between GitHub and repo policy
  • checking which operational project views are available

Source Of Truth

  • Config: docs/project-management/project-18-config.yaml
  • Policy: docs/project-management/project-18-policy.md
  • Apply script: scripts/project/apply_project_18.sh
  • Verify script: scripts/project/verify_project_18.sh

Read the policy first if the request changes milestone grouping or field conventions.

Workflow

  1. Inspect the current state with: scripts/project/verify_project_18.sh
  2. If the request changes the intended state, update: docs/project-management/project-18-config.yaml
  3. Apply the configured GitHub state with: scripts/project/apply_project_18.sh
  4. Re-run verification.
  5. If views are missing or drifted, use the policy doc to reconcile against the existing GitHub default views and then verify again.

Important Rules

  • Treat the repo config as the canonical plan, not the current GitHub state.
  • Do not hand-edit individual issue fields first and backfill config later.
  • Use the apply script for milestone and field updates to keep history reproducible.
  • Keep deferred items in deferred milestones unless the config changes.

View Boundary

GitHub public APIs do not currently offer a complete Project V2 view-management surface. This skill therefore treats the existing GitHub views as canonical and verifies these operational views:

  • Team items
  • Backlog
  • Roadmap

Install

Use scripts/project/install_skill.sh to symlink this repo-owned skill into ~/.codex/skills.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.