Repository navigation
feat: release PAACM 3.1.0 with project extensions - #3
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PAACM 3.1.0 adds project extensions: a repository adds its own rules to any phase of the
paacmskill 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
SKILL.mdstates the general rule.paacm-verifyandpaacm-reviewread the07-verifyand08-reviewextensions. The session-start hook lists the extensions present, for Claude Code and Cursor.paacm task review-inputcopies the## Reviewer checklistsection of.agent/extensions/08-review.mdintoreview-input.md, and thepaacm-revieweragent checks each item.ALGORITHM.mdsection 15 and ADR 0016..agent/extensions/**is in the default protect list.paacm doctorwarns about extensions whose name matches no reference (the agent would never read them).doctoralso warns about extensions an explicit protect list does not cover (3.0 installs).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.Verification
npm test: 86 tests pass (80 before). The new tests cover:review-input.md, including CRLF;doctor's two warnings;paacm validate,paacm build --check(58 files), markdownlint-cli2 0.23.3 and the link test pass.claude plugin validate --strictpasses for the plugin and the marketplace.After merge
Tag
v3.1.0on the merge commit and publish the release.v3.0.0is already tagged on914cc1e.Upgrade note
An untouched
.agent/paacm.jsonis updated bypaacm upgrade. If you changed it, add".agent/extensions/**"toprotect.configbefore adding extensions;paacm doctorreports when it is missing.