cy-web-docs-impact

What problem does it solve?

It prevents backend work from accidentally breaking the web UI, docs, agent operability surfaces, extensibility contracts, or config.toml lifecycle by forcing an explicit, concrete downstream impact audit.

Core Features & Use Cases

• Impact-first backend task auditing: Audits a single task file or an entire _techspec.md to determine exactly which web/docs/agent/config surfaces are affected.
• Trigger-driven scope detection: Scans the task’s enumerated “touched” files against the canonical trigger list (including hard co-ship requirements like contract changes).
• Concrete, list-based impact append: Produces/updates ### Web/Docs Impact and ### Extensibility / Agent Manageability / Config Lifecycle subsections with explicit file/path lists, including an explicit “none” case.
• Web surface mapping: Identifies affected web/src/systems/<system>/ modules (adapters, types, query keys/options, hooks, components), generated TS types, MSW fixtures, and Storybook stories, and cross-checks web skill dispatch rules.
• Site and agent surface mapping: Links touched CLI verbs/endpoints/config keys to the relevant packages/site/content/... MDX pages and ensures CLI doc generation co-ship is flagged when required.

Quick Start

Use this skill to audit a backend task spec you’re drafting by providing its path or a _techspec.md, so it appends explicit downstream web/docs and agent/config impact evidence to the task.