Skip to content

feat: release PAACM 3.1.0 with project extensions - #3

Merged
Hyper-AI-Lab merged 2 commits into
mainfrom
feat/project-extensions
Oct 17, 2026
Merged

Hyper-AI-Lab merged 2 commits into
mainfrom
feat/project-extensions

Conversation

@Hyper-AI-Lab

Copy link
Copy Markdown
Owner

Summary

PAACM 3.1.0 adds project extensions: a repository adds its own rules to any phase of the paacm skill in .agent/extensions/<reference file name>, without forking the kit. A team that already has its own agent workflow (a knowledge base to consult, a roadmap to respect, specialist reviewers, a review checklist, a learnings step) maps it onto PAACM's phases, so the two run as one process instead of competing.

What changes

  • Loading at the right moment. Each of the 18 references ends with the line that tells the agent to read its extension, and a content test enforces it. SKILL.md states the general rule. paacm-verify and paacm-review read the 07-verify and 08-review extensions. The session-start hook lists the extensions present, for Claude Code and Cursor.
  • Subagents get what they need.
    • paacm task review-input copies the ## Reviewer checklist section of .agent/extensions/08-review.md into review-input.md, and the paacm-reviewer agent checks each item.
    • The explore reference tells the writer to put the explore extension's requirements in the explorer's brief.
  • Gates stay intact. An extension adds steps, fields, reviewers and checks, and never removes or weakens a gate; on a conflict the gate wins. This is recorded in ALGORITHM.md section 15 and ADR 0016.
  • Protection and health checks.
    • .agent/extensions/** is in the default protect list.
    • paacm doctor warns about extensions whose name matches no reference (the agent would never read them).
    • doctor also warns about extensions an explicit protect list does not cover (3.0 installs).
  • Docs. New docs/guide/extending.md: where each kind of project rule belongs, how to merge an existing team workflow, a knowledge base, a roadmap, Cursor notes and a worked example. Plus the CHANGELOG with an upgrade note, the README and the requirements traceability.
  • Wording. The always-on block says "PAACM 3" instead of "PAACM 3.0".
  • Version. 3.1.0, with the plugin and marketplace manifests regenerated.

Verification

  • npm test: 86 tests pass (80 before). The new tests cover:
    • the extension line in every reference;
    • the session-start listing in both IDE payloads, and protect asking (Claude Code) or denying (Cursor) on extensions;
    • the checklist in review-input.md, including CRLF;
    • doctor's two warnings;
    • init, upgrade and uninstall leaving extensions intact, including a simulated 3.0 install upgraded to the protected pattern.
  • paacm validate, paacm build --check (58 files), markdownlint-cli2 0.23.3 and the link test pass.
  • claude plugin validate --strict passes for the plugin and the marketplace.

After merge

Tag v3.1.0 on the merge commit and publish the release. v3.0.0 is already tagged on 914cc1e.

Upgrade note

An untouched .agent/paacm.json is updated by paacm upgrade. If you changed it, add ".agent/extensions/**" to protect.config before adding extensions; paacm doctor reports when it is missing.

A project adds its own rules to any reference of the paacm skill in
.agent/extensions/<reference file name>, for example
.agent/extensions/01-intake-triage.md. This is where a knowledge base
to consult, a roadmap to respect, specialist reviewers, a review
checklist or a learnings step belong, so that a repository's existing
workflow and PAACM run as one process.

- Every reference now ends with the line that tells the agent to read
  its extension, and the content test enforces it. paacm-verify and
  paacm-review read 07-verify and 08-review. The session-start hook
  lists the extensions present, for Claude Code and Cursor.
- Subagents get what they need. paacm task review-input copies the
  "## Reviewer checklist" section of the review extension into
  review-input.md, and the reviewer checks each item. The explore
  reference tells the writer to put the explore extension's
  requirements in the explorer's brief.
- Extensions are protected configuration: .agent/extensions/** is in
  the default protect list. doctor warns about names that match no
  reference and about extensions an explicit protect list does not
  cover (installs made before this release).
- An extension adds steps, fields, reviewers and checks and never
  removes or weakens a gate; on a conflict the gate wins. ALGORITHM.md
  section 15 and ADR 0016 record the rule, and docs/guide/extending.md
  shows where each kind of project rule belongs, how to merge an
  existing team workflow, and a worked example.
- The always-on block says "PAACM 3" rather than "PAACM 3.0".
Version 3.1.0 in package.json and src/content/kit.json, with the
regenerated plugin and marketplace manifests. The CHANGELOG describes
project extensions and the upgrade note for 3.0 installs whose
paacm.json lists protect.config explicitly. The README status line and
the requirements traceability record the release; two tests now read
the expected version from package.json instead of hardcoding it.
@Hyper-AI-Lab
Hyper-AI-Lab merged commit 8d1cd5c into main Oct 17, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant