Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

pce-memory-project-manager

Estrellas3

Forks0

Actualizado24 de marzo de 2026 a las 14:08

Manage CAPHTECH/pce-memory GitHub issue, milestone, and Project

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

CAPHTECH

CAPHTECH/pce-memory

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Gerentes de sistemas informáticos y de informaciónOcupaciones de dirección y gestión·SOC 11-3021

SKILL.md

readonly

name	pce-memory-project-manager
description	Manage CAPHTECH/pce-memory GitHub issue, milestone, and Project

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

Inspect the current state with: scripts/project/verify_project_18.sh
If the request changes the intended state, update: docs/project-management/project-18-config.yaml
Apply the configured GitHub state with: scripts/project/apply_project_18.sh
Re-run verification.
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.

Más de este repositorio

mismo repositorio

pce-core

CAPHTECH/pce-memory

Core pce-memory v2 workflow skill. Guides raw observe, distill/promote, intent-aware activate, feedback, rollback, and the narrow upsert escape hatch. Triggered by: 'memory workflow', 'activate context', 'record to memory', 'promotion pipeline'.

2026-03-253

pce-promotion

CAPHTECH/pce-memory

Dedicated pce-memory v2 promotion pipeline skill. Guides distill -> promote -> rollback with candidate lineage, reviewer metadata, and durable repair rules. Triggered by: 'promotion pipeline', 'distill memory', 'promote candidate', 'rollback claim'.

2026-03-243

pce-sync

CAPHTECH/pce-memory

Team knowledge synchronization skill for pce-memory v2. Manages push/pull/status with memory_type-aware export/import and layer-aware sync rules. Triggered by: 'sync knowledge', 'push knowledge', 'pull team knowledge', 'check sync status'.

2026-03-243

pce-graph

CAPHTECH/pce-memory

Knowledge graph operations skill for pce-memory. Create, query, and visualize entities and relations. Triggered by: 'create entity', 'graph relation', 'query knowledge graph', 'map dependencies'.

2026-03-183

name	pce-memory-project-manager
description	Manage CAPHTECH/pce-memory GitHub issue, milestone, and Project

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

Inspect the current state with: scripts/project/verify_project_18.sh
If the request changes the intended state, update: docs/project-management/project-18-config.yaml
Apply the configured GitHub state with: scripts/project/apply_project_18.sh
Re-run verification.
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.