Results for “adr”

Build a RoadRunner Scenario programmatically from an OpenSCENARIO 1.x (.xosc) file using the `roadrunner-scenario-authoring` skill. Use when the user wants to recreate a scenario from a .xosc file, interpret an OpenSCENARIO file and build it programmatically, reconstruct a .xosc as a RoadRunner scenario, generate a MATLAB script from a .xosc file, or convert an OpenSCENARIO file to MATLAB code. Do NOT use when the user says "import" a .xosc file — that means they want RoadRunner's built-in importScenario API, not programmatic reconstruction. Handles position translation (LanePosition and RoadPosition to world coordinates), construct mapping, relative references, trajectory/route handling, parameter expressions, catalog references, and phase logic topology.

The English summary is being prepared. Showing the original description.

Foundation skill for all RoadRunner workflows: MATLAB path setup, connection, project/scene/scenario lifecycle, world settings, handle management, status, and close. Use when connecting to RoadRunner, managing projects/scenes/scenarios, setting world origin, checking status, closing RoadRunner, or when any downstream RoadRunner skill needs initialization.

The English summary is being prepared. Showing the original description.

Writes architecture decision records (ADRs) and keeps the rest of a project's documentation true after a change: README, reference comments on public interfaces and the changelog. Use when a user says "write an ADR", "record this decision", "document why we chose X", "set up a decision log", "supersede the old decision", "update the README", "add a changelog entry" or "document this API". Produces records in the Nygard or MADR format, a Keep a Changelog entry, and a script that checks the log for gaps and broken supersession links.

The English summary is being prepared. Showing the original description.

Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.

The English summary is being prepared. Showing the original description.

Genera un nuevo Registro de Decisión de Arquitectura (ADR) copiando la plantilla de ADR en el siguiente archivo numerado y registrándolo en el índice de decisiones. Úsalo cuando la persona quiera registrar una decisión de arquitectura, crear/añadir un ADR o documentar una elección técnica (p. ej. "escribe un ADR para cambiar la base de datos", "añade un registro de decisión").

The English summary is being prepared. Showing the original description.

This skill recommends lifelong biochemical testing for recurrence in all patients with Cushing's syndrome after adrenalectomy, except those with resected adrenal adenoma showing CT density <10 Hounsfield units. Use when determining long‑term follow‑up strategy for a post‑adrenalectomy CS patient; triggers include “post‑adrenalectomy Cushing’s syndrome”, “CT density <10 HU”, and “adrenal adenoma resection”.

The English summary is being prepared. Showing the original description.

This skill guides evaluation for malignancy using imaging in patients with a history of adrenal adenoma (post‑adrenalectomy Cushing’s syndrome) when the adenoma demonstrates a CT density of ≥10 Hounsfield units or when pathology is consistent with possible carcinoma. Trigger phrases include “CT density ≥10 HU”, “possible carcinoma on pathology”, and “post‑adrenalectomy CS patient with adrenal adenoma history”.

The English summary is being prepared. Showing the original description.

Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.

• Sharpening a plan through detailed questions
• Examining a design through an interview
• Documenting design decisions during discussion

Route broad requests about project documentation to a suitable specialist skill. When requested, run a read-only audit of document roles, local links, architecture decision indexes, and evidence references, reporting failures and items needing review.

• Choose a workflow for organizing project documentation
• Identify existing documentation sources
• Audit local links and architecture decision indexes

Investigate a Homecore capability by tracing relevant source files, tests, and accepted architecture decisions. Check documented status and limitations before proposing code, while keeping implementation presence separate from deployment compatibility or claims of Home Assistant parity.

• Find source files and design decisions for a Homecore capability
• Check documented implementation status and limitations
• Review focused tests before proposing code changes

Investigate a username, file, code identifier, URL, or concept by exploring connected entities across relevant sources. Produce a dossier with a summary, relationship diagram, source references, and a machine-readable JSON graph.

• Mapping connections around a username or concept
• Investigating references to a file or code identifier
• Tracing links to an architecture decision record

Use ROADrecon and roadtx during authorized Microsoft Entra ID testing to inspect directory objects and authentication tokens, which represent access permissions. Explore collected configuration offline, test token exchanges, and assess conditional access and device controls.

• Mapping tenant users, groups, roles, and applications
• Reviewing conditional access policies
• Testing token exchanges and device-based single sign-on

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.

• Compare technologies before choosing one
• Document the reasoning behind a design decision
• Review a proposed system design

Design and review system architecture, compare databases and structural approaches, and document technical decisions. Included tools generate architecture diagrams, inspect dependencies, and assess project structure to identify circular relationships, excessive coupling, and opportunities for improvement.

• Comparing monolith and microservices approaches
• Choosing a database for project requirements
• Generating diagrams from an existing project

Check whether development tasks are ready for implementation by reviewing acceptance criteria, design decisions, dependencies, and required evidence. Receive one of four verdicts for each task, with specific gaps and suggested fixes.

• Checking a task before assigning implementation
• Reviewing all tasks in the current sprint
• Finding ambiguous acceptance criteria

Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Create and organize API documentation, READMEs, onboarding guides, and architecture decision records that explain design choices. Structure content around readers’ tasks, with consistent terminology, complete code examples, and separate sections for instructions, reference details, and explanations.

• Writing a README with installation and quick-start instructions
• Documenting API parameters, return values, and errors
• Recording architecture decisions and their consequences

Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.

• Build planning files from existing project documents
• Add documented requirements and phases to an existing plan
• Identify conflicting statements across planning documents

Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.

• Compare technologies before choosing one
• Document the reasoning behind a design decision
• Review a proposed system design

Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

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. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Inspect ADR health read-only; optionally select one ADR with --adr N.

The English summary is being prepared. Showing the original description.