feat(systemplane): refactor migration skill for lib-commons v5 API
docs(plugin): update skill counts and keywords for new deck skill
chore(plans): remove obsolete caching and dev-cycle plan documents
Migrate authoritative sources, standards, skills, and platform mirrors from lib-commons v2/v4 to v5.0.2. ~215 line-level replacements across 26 files.
- Authority chain aligned: README, backend-engineer-golang, standards-coverage-table, and dev-team/docs/standards/golang/* now declare v5 as current.
- Code examples and import paths updated from lib-commons/v2/... and lib-commons/v4/... to lib-commons/v5/....
- Header notices added to preserve historical bodies of dev-systemplane-migration (v5 systemplane rewrite flagged), .archive/migrate-v4 (completed v2/v3 to v4 migration), and docs/plans/2026-04-14-caching-cqrs-standards (archived plan).
- OpenCode Version Gate: removed false claim that cassert, cruntime, csafe, cbackoff, and coutbox were introduced in v5 (they are v4); callout now lists v2/v3/v4 as legacy below the v5 standard.
X-Lerian-Ref: 0x1
Generated-by: Claude
AI-Model: claude-opus-4-7
Propagates the 10-reviewer peer list across agent frontmatter, Position/Critical prose, shared-patterns, skill dispatchers, gate validators, and docs — resolving drift left behind when multi-tenant-reviewer and lib-commons-reviewer were added to the pool. Also fixes broken shared-pattern paths in lib-commons-reviewer and adds substantive blocker criteria to multi-tenant-reviewer plus codebase-context severity heuristic (Lerian third-rail vs external recommendation) to lib-commons-reviewer.
X-Lerian-Ref: 0x1
Cross-reference audit after v1.56.0 found stale references to the removed Gate 0.5 dispatch. Critical: validate-gate-progression.sh was reading .delivery_verification.status from TASK level (no longer populated), firing false errors on every real cycle. Now reads subtask-level .gate_progress.implementation.delivery_verified. dev-cycle/SKILL.md self-description (frontmatter, overview, cannot-skip block) updated from "11 gates (0→0.5→1→...→9)" to the three-cadence model. using-dev-team marks ring:dev-delivery-verification DEPRECATED. dev-refactor-frontend artifact description swaps "1:1 mapped" for clustering.
Public docs (CLAUDE.md, README.md, WORKFLOWS.md) updated to describe subtask/task/cycle cadence instead of old per-unit linear flow. file-size-enforcement.md dispatch point corrected from Gate 0.5 to Gate 0 exit criteria (ring:dev-implementation Step 7).
Stripped meta-narration markers ("since R4", "formerly Gate 0.5", "since Prancy Bentley speedup", "absorbed from former...") from skill bodies. Skills describe current behavior; edit history lives in CHANGELOG and git log, not in agent context.
X-Lerian-Ref: 0x1
Authoritative implementation plan for reclassifying gate cadence in dev-cycle and dev-refactor. Target: ~40-50% wall-clock reduction without reducing reviewer count, coverage thresholds, or quality gates.
X-Lerian-Ref: 0x1
Planning document for the caching/CQRS standards work still referenced the old 7-reviewer codereview flow in Tasks 6, 11, and 15. Updated all three dispatch blocks to 8 reviewers and added ring:performance-reviewer to each reviewer list. Task 15 dispatch block was also normalized to match Task 6/11 formatting (inline reviewer list).
X-Lerian-Ref: 0x1
Generated-by: Claude
AI-Model: claude-opus-4-7
Update all skills, agents, shared patterns, docs, and platform configs that still referenced 7 code review agents to reflect the 8th reviewer (ring:performance-reviewer). Includes agent self-descriptions, dispatch instructions, anti-rationalization tables, slicing math, gate tables, and opencode schema definitions.
X-Lerian-Ref: 0x1
feat(hooks): add schema validator and enhance skill generation
refactor(*): align all components with the new frontmatter schema
refactor(commands): replace arguments object with simple argument-hint
refactor(agents): remove invalid version field from agent frontmatter
test(hooks): add unit tests for frontmatter validation and generation
Introduces a new parallel reviewer, `ring:dead-code-reviewer`, to
systematically identify orphaned code resulting from changes. This
enhances codebase hygiene by detecting unused helpers, types, and
tests, thereby reducing technical debt and improving maintainability.
The parallel code review system is expanded from 6 to 7 concurrent
reviewers. All related workflows, skills, commands, and documentation
have been updated to integrate this new capability.
- Add the `ring:dead-code-reviewer` agent, which analyzes code across
three concentric rings (target, direct dependents, ripple effect) to
find unreachable code.
- Update the `/ring:codereview` command and `ring:requesting-code-review`
skill to dispatch all 7 reviewers in a single parallel step.
- Adjust project documentation, including architecture diagrams, manuals,
and agent guides, to reflect the 7-reviewer workflow.
Removes the hard-coded `model: "opus"` requirement from all agent
definitions, skill examples, and command documentation. The orchestrator
is now responsible for model selection, making the agent framework more
flexible and model-agnostic.
Key changes include:
- Removing the `model` parameter from all agent frontmatter and Task
tool examples.
- Deleting the "Model Requirement" hard gate and self-verification
sections from all agent prompts. This simplifies the prompts and
removes model-specific enforcement logic.
- Updating core documentation (ARCHITECTURE, MANUAL, README) to reflect
that model selection is an orchestrator concern.
- Removing redundant `changelog` and `last_updated` fields from agent
frontmatter, as this information is tracked by source control.
This architectural shift allows the orchestrator to dynamically choose
the best model for a given task based on complexity, cost, or speed,
without being constrained by the agent's definition. It simplifies
agent maintenance and prepares the system for easier integration of
future AI models.
The codereview pre-analysis pipeline is refactored to use 'mithril',
an external tool installed via 'go install'. The previous system of
pre-built, in-repo binaries with its custom build workflow and
checksum verification is removed. This change simplifies maintenance
and improves security by leveraging the Go ecosystem's checksum DB.
The visual-explainer skill is refactored to use the '@pierre/diffs'
library for rendering code diffs, replacing the hand-rolled CSS
panels. This provides a more professional and feature-rich
visualization with word-level diffs and Shiki syntax highlighting.
Finally, obsolete audit and handoff documents are removed, and a help
message in the install script is updated to be accurate.
The previous 10-gate workflow lacked specific validation for multi-
tenant environments. To improve software reliability and ensure data
isolation between tenants, a dedicated multi-tenancy gate is necessary.
This change introduces a new "multi-tenant" gate into the `dev-cycle`
workflow, immediately following the implementation gate. This expands the
process from 10 to 11 gates. All related documentation has been
updated to reflect this new, more robust development cycle.
Code reviews that focus only on changed files can miss how those
changes break other parts of the codebase. Callers, contract
consumers, and dependent modules can be inadvertently affected, leading to
bugs that are difficult to detect in a localized review.
This commit introduces a new agent, `ring:consequences-reviewer`, to
systematically trace these "ripple effects." Its purpose is to analyze
the downstream impact of code changes by walking caller chains and
verifying consumer contracts.
The core parallel code review workflow, orchestrated by the
`/ring:codereview` command, now dispatches six agents in parallel
instead of five. All related documentation, skills, and agent prompts
have been updated to reflect this more robust 6-reviewer process.
The parallel code review process expands from 3 to 5 reviewers to
enhance code quality. This introduces `ring:test-reviewer` and
`ring:nil-safety-reviewer` to provide deeper analysis of test coverage
and null safety patterns, improving overall reliability.
The `dev-cycle` workflow is upgraded from a 6-gate to a 10-gate process,
incorporating a sophisticated suite of automated testing gates:
- Unit Testing (Gate 3)
- Fuzz Testing (Gate 4)
- Property-based Testing (Gate 5)
- Integration Testing (Gate 6)
- Chaos Testing (Gate 7)
This change establishes a much higher standard for testing and ensures
features are more resilient and production-ready.
Finally, new agents and commands are added to the PMO and Product plugins
to support delivery tracking, design validation, and reporting, further
extending the system's capabilities across the development lifecycle.
All documentation is updated to reflect these enhancements.
Transform all user-facing Ring component references from colon-based
notation (ring:) to a standardized hyphen-based format (ring-).
This change affects skill names, agent names, and slash commands in all
documentation, guides, and examples. The goal is to create a consistent
and user-friendly namespace that is easier to read and type.
For example:
- Skill/Agent references like `ring:code-reviewer` become `ring-code-reviewer`
- Slash commands like `/ring:codereview` become `/ring-codereview`
The colon-based format (`ring:`) is intentionally preserved in YAML
frontmatter (`name: ring:skill-name`) for internal metadata, separating
the user-facing display name from the internal tooling identifier.
Improves the handoff workflow by automatically resuming recent handoffs
when a new session starts. This eliminates the need for users to
manually run `/ring:resume-handoff` after clearing the context, creating
a smoother and more intuitive user experience.
The `session-start.sh` hook now detects a `.pending` breadcrumb file,
created by the `create-handoff` command, in the `docs/handoffs`
directory.
- If the handoff is less than one hour old, its content is automatically
loaded into the session's context and the user is notified.
- If it is older, the user is prompted to decide whether to resume it.
- A new `.gitignore` file prevents committing the temporary `.pending` file.
This change also introduces several supporting improvements:
- Adds a debug logging mechanism enabled by the `RING_DEBUG` shell
variable to simplify troubleshooting hook execution.
- Replaces `cat <<EOF` with `printf` for safer JSON generation,
preventing script failures from special characters in variables.
- Prioritizes the `CLAUDE_PROJECT_DIR` environment variable for project
root detection, adding flexibility for different run environments.
Renames docs/refactor/ to docs/ring:dev-refactor/ to match the skill namespace. Defines explicit timestamp format YYYY-MM-DDTHH:MM:SS for consistent directory naming.
X-Lerian-Ref: 0x1
Removes all rate limiting and CORS references across agents, skills, commands, and standards. These features had no dedicated standard — only scattered checklist items and examples. Cleans up 17 files including security-reviewer checklist, API doc status codes, severity examples, and log examples.
X-Lerian-Ref: 0x1
Updates documentation to reflect the 7-gate development cycle model:
- CLAUDE.md: Update slash command and workflow table descriptions
- dev-cycle/SKILL.md: Change header from 6-gate to 7-gate orchestrator
- WORKFLOWS.md: Update Development Cycle section to 7-gate with Gate 3.5 listed
Gate 3.5 (integration-testing) is optional and runs when external dependencies or integration scenarios exist.
X-Lerian-Ref: 0x1
Expands the FinOps plugin to include cost management, which is a core
pillar of the discipline. This provides users with a new capability to
plan and optimize infrastructure spending.
This change introduces the `infrastructure-cost-estimator` agent and
its corresponding `infrastructure-cost-estimation` skill. All project
documentation is updated to reflect the new agent, skill, and the
incremented total counts.
The webinar this outline was created for has already occurred.
This planning document is no longer relevant and is being removed to
reduce repository clutter.
Update all documentation that shows agent dispatch patterns to remove
explicit model parameter. Model selection is delegated to orchestrators.
X-Lerian-Ref: 0x1
Deleted several obsolete documentation files related to the Ring Continuity project, including:
- BFF Pattern Decision Support Implementation Plan
- Module-Aware Documentation Placement Implementation Plan
- API Design, Data Model, Dependency Map, Feature Map, Product Requirements Document, Research Phase, Subtask Breakdown, Task Breakdown, and Technical Requirements Document.
These files are no longer relevant to the current project structure and workflow, streamlining the documentation repository.
- Updated framework specifications in frontend-bff-engineer-typescript and frontend-engineer to reflect version policy for Next.js, clarifying usage for new and existing projects.
- Introduced a new ui-engineer agent to handle UI implementation from product-designer outputs, ensuring compliance with design specifications and UX criteria.
- Added detailed documentation for the ui-engineer, including technical expertise and required outputs for effective UI development.
This enhances clarity in framework usage and establishes a dedicated role for translating design specifications into production-ready components.
Session handoffs documenting the development of:
Phase 4: Data flow analysis implementation
- Complete data-flow analyzer for Go with taint tracking
- Integration with pipeline phases
Phase 5: Context compilation and dogfooding
- Context compiler that generates reviewer-specific markdown
- Pipeline orchestrator coordinating all 6 phases
- Comprehensive dogfooding with 5 parallel reviewers
- All 30 identified issues fixed and validated
Includes raw code review output from dogfooding session.
X-Lerian-Ref: 0x1
feat(codereview): add call graph analyzers for Go, TS, and Python
feat(codereview): add JSON output and markdown impact summary report
docs(codereview): add handoff documents for phase 2 and 3
test(codereview): add unit and integration tests for call graph feature
refactor(*): standardize all agent and skill names with `ring:` prefix
docs(*): update all documentation to use new `ring:` prefix for names
Introduce a new `static-analysis` Go binary to automate the execution
of linters as the first phase of an automated code review process. This
tool provides a consistent, language-aware way to detect issues early.
The key motivations are to:
- Standardize linting across different languages.
- Automate the detection of bugs, style issues, and vulnerabilities.
- Provide a structured data output for subsequent review phases.
This implementation includes:
- A CLI entry point to orchestrate the analysis process.
- A common `Linter` interface and registry for easy extension.
- Wrappers and parsers for 9 linters:
- Go: golangci-lint, staticcheck, gosec
- TypeScript: tsc, eslint
- Python: ruff, mypy, pylint, bandit
- Normalization of linter output into a unified JSON format with
consistent severity and category mapping.
- Filtering of findings to report only issues in changed files from the
input scope.
- Extensive unit tests for parsers and integration tests for the
end-to-end flow.
docs(commands): add 'ring:' prefix to all command invocations
build(deps): remove requirements.txt in favor of dependency-map.md
chore(docs): remove obsolete handoff for namespace refactoring
Updates all skill, agent, and command invocations across active and archived plugins to use the ring: prefix consistently. This ensures namespace uniformity throughout the codebase.
X-Lerian-Ref: 0x1
This commit restructures the plugin ecosystem to improve maintainability,
simplify component invocation, and focus on high-value domains.
Key changes:
- **Unified Namespace:** All component invocations are standardized to the
`ring:{component}` format, replacing the verbose `ring-{plugin}:...`
prefix. This simplifies usage and abstracts the internal plugin
structure.
- **Archive Legacy Plugins:** The `finance-team`, `ops-team`, `pmm-team`,
and `pmo-team` plugins are moved to a new `.archive` directory.
These plugins contained complex, outdated patterns and are now
preserved for historical reference only.
- **Introduce FinOps Plugin:** A new, highly-focused `finops-team` plugin
is added to handle Brazilian financial regulatory compliance (BACEN,
RFB), consolidating critical functionality into a more focused package.
- **Update Documentation:** Core documentation (`ARCHITECTURE.md`,`README.md`,
`CLAUDE.md`, `MANUAL.md`) and the plugin marketplace are updated to
reflect the new structure and unified namespace.
This major refactoring archives 5 non-core plugins to simplify the
project's focus and reduce maintenance overhead. The goal is to
concentrate on the primary software delivery value chain: Product
Planning -> Development -> Documentation.
The following plugins have been moved to the `.archive/` directory:
- ring-finance-team
- ring-finops-team
- ring-ops-team
- ring-pmm-team
- ring-pmo-team
This change reduces the number of active plugins from 9 to 4.
Key changes include:
- Updating `.claude-plugin/marketplace.json` to remove archived plugins.
- Updating all top-level documentation (README, ARCHITECTURE, MANUAL) to
reflect the new, focused set of 4 plugins.
- Deleting obsolete development plans and handoffs associated with the
archived plugins.
- Removing cross-plugin references from the remaining active plugins.
- Updating the installer script to remove mentions of archived plugins.
By archiving this code instead of deleting it, we preserve the work
for future reference while cleaning up the active codebase.
