Skip to content

feat(plugin): ship the workflow rules that lived only in CLAUDE.md - #67

Merged
chrispezza merged 1 commit into
mainfrom
feat/ship-runtime-rules
Oct 12, 2026
Merged

chrispezza merged 1 commit into
mainfrom
feat/ship-runtime-rules

Conversation

@chrispezza

@chrispezza chrispezza commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Closes #62. Four rules about how the plugin behaves existed only in this repo's CLAUDE.md, so plugin users never got them.

  • New Workflow Rules section in plugin/docs/registry-operations.md, the bundled doc every workflow skill already reads:
    • Tier escalation is offered, never applied: list the phase's Tier 2 prompts, run only what the user picks, return to the Tier 1 sequence
    • Never auto-escalate to Tier 3
    • When a context_gated condition is unclear, ask the user
    • Entry points are exclusive
  • All four workflow skills reference the section instead of restating it.
  • The "Runtime rules that exist only here" section is removed from CLAUDE.md.
  • Plugin version 0.5.0 to 0.5.1.

Behaviour change for plugin users

  • product-ideation: on an escalation signal it used to insert the phase's Tier 2 prompts. It now offers them and runs only what the user picks.
  • product-flow and tech-spec: listed Tier 2 prompts with no procedure. They now follow the same one.
  • ux-optimization: already offered branches; it gains the unclear-gate rule.

Not changed

skills-claude-ai/ (the Claude.ai ports) is untouched. Those ports already offer Tier 2 prompts as optional branches, so this change brings the plugin in line with them.

Test plan

  • python checks/run_checks.py --ci — 18 checks, 0 findings (self-containment clean: new references use ${CLAUDE_PLUGIN_ROOT})
  • claude plugin validate --strict ./plugin passes
  • python -m unittest discover -s checks/tests passes
  • Manual runbook walkthrough of an escalation in a fresh session: not done
  • CI green

ADR impact

  • Existing ADRs amended by appended, dated sections: 0006, 0019

🤖 Generated with Claude Code

Four rules about plugin behaviour existed only in this repo's CLAUDE.md, so
plugin users never received them (issue #62).

- Add a Workflow Rules section to the bundled registry-operations doc: tier
  escalation is offered and the user picks, never auto-escalate to Tier 3,
  ask when a context_gated condition is unclear, entry points are exclusive
- Point all four workflow skills at it; product-ideation no longer inserts
  Tier 2 prompts on a signal, product-flow and tech-spec gain the procedure
- Remove the unshipped-rules section from CLAUDE.md
- Append amendments to ADRs 0006 and 0019; bump the plugin to 0.5.1

Closes #62

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chrispezza
chrispezza merged commit 9985cc8 into main Oct 12, 2026
2 checks passed
@chrispezza
chrispezza deleted the feat/ship-runtime-rules branch October 12, 2026 18:12
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.

Move the runtime rules that live only in CLAUDE.md into the plugin

1 participant