@unbrained/pm-cli 2026.9.27 → 2026.9.28

package/plugins/pm-claude/commands/pm-release.md

@@ -1,41 +0,0 @@
----
-description: Run pm release-readiness — validation, coverage gate, changelog check, GitHub CI verification — with live TUI tracking. Accepts an optional version or release item ID as argument.
----
-
-Run the full pm release workflow using native MCP tools. Argument: `$ARGUMENTS` (optional: version like `v1.2.3`, or pm item ID for an existing release item).
-
-1. **Find or create the release item**:
-   - `pm_search` with query "release" to find existing release items.
-   - If `$ARGUMENTS` is a pm ID: `pm_get` it directly.
-   - If no match: `pm_create` with `type: "Chore"`, `title: "Release <version>"`, `priority: "0"`.
-2. **Claim** with `pm_claim`.
-3. **Sync to Claude Code task panel**:
-   ```
-   TaskCreate:
-     subject: "[pm-xxxx] Release: <version>"
-     description: "Release gate tracking — pm-xxxx"
-     activeForm: "Running release gates"
-   ```
-   Call `TaskUpdate(in_progress)`. Save the taskId.
-4. **Link release artifacts**:
-   - `pm_docs` — link `CHANGELOG.md`
-   - `pm_files` — link `package.json`
-5. **Run gates** (all must pass before tagging):
-   - `pnpm build`
-   - `node scripts/run-tests.mjs coverage`
-   - `pm_validate` with `checkResolution: true, checkHistoryDrift: true, checkFiles: true`
-   - `pm_health`
-   - `node scripts/release/run-gates.mjs` (if present)
-6. **Record gate results** with `pm_comments`:
-   ```
-   "Release evidence: build ok. N tests pass. 100% coverage. pm validate ok. pm health ok."
-   ```
-7. **Tag and push** (if all gates pass):
-   ```bash
-   git tag v<version> && git push origin v<version>
-   ```
-8. **Verify CI** — `gh run list --limit 5` and confirm all checks are green.
-9. **Post-CI evidence** — add a final `pm_comments` with CI run URL.
-10. **Close** — `pm_close` with reason, `pm_release`, then `TaskUpdate(completed)`.
-
-Do not tag if any gate fails. Report the failing gate and what's needed to fix it.

package/plugins/pm-claude/commands/pm-workflow.md

@@ -1,49 +0,0 @@
----
-description: Run the pm workflow loop — orient, claim, track, and close a pm item — with full hybrid TUI display. Accepts an optional item ID or description as argument.
----
-
-Run the pm workflow loop using native MCP tools. Argument: `$ARGUMENTS` (item ID, keywords, or description of new work).
-
-This is the general-purpose pm workflow command. For specialized loops use:
-- `/pm-developer` — implementation/coding work
-- `/pm-release` — release gates and publishing
-- `/pm-planner` — backlog planning and decomposition
-- `/pm-audit` — tracker health audit
-
-**Steps:**
-
-1. **Orient**:
-   ```json
-   { "tool": "pm_context", "args": { "options": { "limit": "10" } } }
-   ```
-
-2. **Find or create the item** from `$ARGUMENTS`:
-   - pm ID → `pm_get`
-   - Keywords → `pm_search` then pick the best match
-   - Description of new work → `pm_search` first, then `pm_create` if no duplicate
-
-3. **Claim** with `pm_claim`, then `pm_update` to `in_progress`.
-
-4. **Sync to Claude Code task panel**:
-   ```
-   TaskCreate:
-     subject: "[pm-xxxx] <item title>"
-     description: "Tracking pm-xxxx"
-     activeForm: "Working on pm-xxxx"
-   ```
-   Call `TaskUpdate(in_progress)`. Save taskId for this session.
-
-5. **Do the work** — link evidence as you go:
-   - Changed files: `pm_files`
-   - Updated docs: `pm_docs`
-   - Test commands: `pm_test`
-   - Progress notes: `pm_comments`
-
-6. **Verify** — `pm_validate` before closing.
-
-7. **Close**:
-   - `pm_close` with reason addressing acceptance criteria
-   - `pm_release`
-   - `TaskUpdate(completed)` using saved taskId
-
-Report the item ID, title, and final status at the end.