feat: wire change-request, adr, and tutorial follow-up links#125
Conversation
Adds an opt-in /awos:change-request command that captures *why* a previously-agreed requirement changed (trigger, driver, business-level impact) and saves a numbered record under context/change-requests/. - commands/change-request.md + claude/commands/change-request.md wrapper - templates/change-request-template.md - integration hooks: product.md, roadmap.md (offer a CR before writing the artifact) and spec.md (offer a CR when a new spec revises a prior requirement). All hooks are opt-in — the skill opens with a skip option, so existing flows are unchanged unless the user opts in.
Adds an /awos:tutorial command that produces a per-increment learning tutorial for a completed spec: a narrative-first walkthrough plus illustrative code snippets and an optional mermaid diagram. A companion concepts.md ledger dedups concepts against earlier increments so each tutorial teaches only what its increment newly introduced. Supports reconstructing the historical code state via read-only git archaeology when the target spec is not the most recent one. - commands/tutorial.md + claude/commands/tutorial.md wrapper - templates/tutorial-template.md, templates/concepts-template.md - scripts/create-tutorial-directory.sh (mirrors create-spec-directory.sh) - integration hook: verify.md suggests /awos:tutorial after a spec is verified. Hook is a non-blocking suggestion; existing flow unchanged.
Adds an opt-in /awos:adr command that captures an Architecture Decision Record — context, alternatives considered, decision, rationale, and consequences — saved as a numbered file under context/adr/. Bulleted sections (pros/cons, consequences, references) are confirmed by the user via multi-select rather than auto-authored. - commands/adr.md + claude/commands/adr.md wrapper - templates/adr-template.md - integration hooks: architecture.md (offer ADRs after a material architecture change) and tech.md (offer ADRs for architectural choices in a tech spec). Both hooks are opt-in — the skill opens with a skip option, so existing flows are unchanged unless the user opts in.
Restores the cross-skill follow-up suggestions between the three governance/docs skills, now that all three commands exist: - change-request.md suggests /awos:adr when a CR moves an architectural choice - adr.md points to /awos:change-request for pure requirements/scope shifts - tutorial.md suggests /awos:adr when an increment surfaced architectural decisions These links were intentionally omitted from each skill's own PR so that each skill installs and lints standalone. This change must merge AFTER the change-request, adr, and tutorial PRs.
|
Warning Review limit reached
More reviews will be available in 29 minutes and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (17)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Supersedes provectus#122–provectus#125. Following the architectural review in #proj_awos, the three skills ship as a plugin sibling to plugins/awos rather than modifying core commands — keeps the spec→tech→tasks→implement→verify pipeline lean and removes the perpetual upstream-merge conflict surface the prior branches created. Discoverability is bundled with the plugin: a UserPromptSubmit hook declared inline in plugin.json (bug #10225 workaround — hooks/hooks.json does not fire) matches 6 core AWOS phases plus the 3 plugin commands; the awos-next skill conditionally suggests a plugin command via free-text inspection of the just-completed phase's output, staying silent when uncertain. Test additions stay generic: one new Layer 1 assertion that every plugin SKILL.md has valid frontmatter, plus explicit hardcoded entries per plugin-contributed command in the /awos:<name> cross-reference test (independent ground truth, not SUT-derived). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
What
Restores the cross-skill follow-up suggestions between the three governance/docs skills, now that all three commands exist:
change-request.mdsuggests/awos:adrwhen a CR moves an architectural choiceadr.mdpoints to/awos:change-requestfor pure requirements/scope shiftstutorial.mdsuggests/awos:adrwhen an increment surfaced architectural decisionsWhy a separate PR
These three links were intentionally omitted from each skill's own PR so that each skill installs and lints standalone (AWOS's
lint-promptstest requires every/awos:<cmd>reference to resolve to a real command). This PR re-adds them once all three commands are present.Merge this AFTER the three skill PRs:
Until those merge, this PR's diff will also show their commits; once they're in
main, this reduces to the three follow-up lines.Validation
npm test→ 69/69 pass (with all three commands present)npx prettier --check .clean