pm-status

Étoiles17

Forks5

Mis à jour4 juillet 2026 à 15:45

DEPRECATED — superseded by flow-board. Kept as a pointer so old references don't 404. Use flow-board for the claim board + the one next thing.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

pmcfadin

pmcfadin/cqlite

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	pm-status
description	DEPRECATED — superseded by flow-board. Kept as a pointer so old references don't 404. Use flow-board for the claim board + the one next thing.
disable-model-invocation	true
argument-hint	["optional epic number or label"]

pm-status — DEPRECATED (issue #1855)

Superseded by flow-board, which renders the shared GitHub Project claim board (status, assignee, priority), reconciles drift, reaps abandoned claims, and surfaces the single item waiting on the owner — things this older label-only sweep did not do. Use flow-board instead.

Follow-on actions live in the pipeline: flow-finalize (close a merged issue), flow-implement (drive one), the manager/worker commands (run the backlog). Doctrine: docs/development/pm-operating-loop.md.

Plus depuis ce dépôt

même dépôt

flow-address

pmcfadin/cqlite

Resolve PR review comments for an in-review issue — fix them in the issue's worktree, re-run the gate + C as needed, push, and reply per thread. Fourth stage of the CQLite delivery pipeline. Use when the owner leaves PR comments and says "address

2026-07-1817

flow-groom

pmcfadin/cqlite

Turn a rough idea into one scoped, labeled GitHub issue (one P0–P3 + status:ready, testable acceptance criteria), and decide oracle-vs-design routing. First stage of the CQLite delivery pipeline. Use when the owner says "groom <idea>", "file an issue for X", or brings a rough idea to scope.

2026-07-1817

flow-implement

pmcfadin/cqlite

Implement an approved issue — spawn sstable-developer (TDD) in the issue's worktree, run rust-reviewer + roborev on the lite-green diff BEFORE any full gate (review-first is default), open the PR, then hand the endgame (the ONE full gate → C → final roborev → merge-on-green → finalize) to a disposable flow-closer agent so gate/review churn never accretes in the lead session. Third stage of the CQLite delivery pipeline. Requires owner approval of the spec (design-driven) first. Use when the owner says "implement

2026-07-1817

ci-cd-validation-merge-workflow

pmcfadin/cqlite

Pre-push validation checklist (cargo fmt, clippy with zero warnings, feature flag testing, test suite), CI monitoring, merge process, and release quality gates. Use when preparing to push code, validating changes before PR, running CI checks, merging PRs, or preparing releases.

2026-07-1817

flow-board

pmcfadin/cqlite

Report status across all in-flight CQLite delivery work — render the shared GitHub Project claim board (item, status, assignee, priority) with drift + abandoned-claim reconciliation, then surface and drive the single furthest-along item waiting on the owner (a green PR to merge, a spec to approve), or offer a claim-aware pick-list. Use when the owner asks "where do things stand", "what's next", "unblock me", or "what needs me".

2026-07-1817

flow-activate

pmcfadin/cqlite

Activate a groomed design-driven issue — create its worktree + branch (1:1:1:1), run OpenSpec propose to produce proposal/design/specs/tasks, render the spec + recommended design INLINE, then STOP for the owner's approval. This is Seam 1; it never implements. Second stage of the CQLite delivery pipeline. Use when the owner says "activate

2026-07-1817

Exécutez n'importe quel Skill en un clic