Use this skill when implementing a business module or confirming a change to its responsibilities. It helps identify ownership and consumers, connect local instructions to existing domain knowledge and interfaces, and check that links and claims match the code.
Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module documentation setup.
Run score Not tested
See how to installWhen you implement a business module or change an existing module’s responsibilities, this skill helps identify the state it owns, its public interfaces, and the systems or teams that use it. It connects local working rules to project-wide instructions and established sources for terminology, design decisions, API contracts, and change impact. It also compares claims in documents with code and contracts, and checks referenced links.
Use it when a new business area is being implemented as a module, or when a confirmed change in responsibility calls for updates to working rules and knowledge links. For a discussion about module boundaries or a documentation audit alone, it inspects existing information and reports findings without creating files. Ordinary bug fixes, visual changes, and internal refactoring that leaves boundaries unchanged do not start documentation setup.
Checking links requires the audit script from the installed docs-governance skill. New top-level documents are subject to the approval requirements of living-docs-governance.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 30, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.
Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.
Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.