Loading...
Loading...
Found 165 Skills
Create, update, review, and reference architecture decision records (ADRs) in the current git repository. Use when the user asks messy design questions, wants a design doc turned into ADR draft(s), needs existing decisions checked before implementation, wants gaps surfaced before writing an ADR, or wants future sessions to reuse decisions consistently. Inspect repository code and docs first, ask only for missing decision-critical information, then produce or update ADR files using the repo’s ADR conventions or the defaults in references/.
Broadridge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Broadridge data.
Automate Codereadr tasks via Rube MCP (Composio). Always search tools first for current schemas.
Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.
Validate Architecture Decision Records (ADR) against Layer 5 schema standards
Specializes in generating Action-Domain-Responder (ADR) boilerplate for Gravito projects. Trigger this when adding new features or modules using the ADR pattern.
Automated fix skill that reads review reports and applies fixes to ADR documents - handles broken links, element IDs, missing files, and iterative improvement
Create a new Architecture Decision Record in doc/adr/
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. Part of the skills-for-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. Part of the skills-for-java project
CodeREADr integration. Manage data, records, and automate workflows. Use when the user wants to interact with CodeREADr data.