Use AgentBay and $analyze in this isolated synthetic example. Read .agents/skills/agentbay-skill-installer/SKILL.md and the named provider’s installed SKILL.md and relevant resources before work. For a large skill file, read it in bounded consecutive sections so the instructions are not lost to output truncation. The exact provider source is supplied in source-map.json; this is selected-upstream verification, not a catalogue search. All listed sources were fetched at the recorded commit and Git blob checked. Verify the installed hash against the map. Read brief.md and constitution.md. The fixture fixes scope and waives further discovery questions; never claim a real user interview or human approval. Use only this named provider skill plus AgentBay; do not auto-invoke follow-on skills. Do not delegate, access accounts, install extra dependencies, edit installed skills or checks, run downloaded companion scripts, commit or deploy. Preserve each prior stage’s files.

Apply the analyze skill as a strictly read-only pre-implementation audit. All required inputs are present: specs/feature.json points at specs/onboarding; constitution.md and spec.md/plan.md/tasks.md/tasks.json are supplied. Follow its coverage, consistency and constitution checks. No cloud resources are declared, so Azure provisioning is outside this example. Output the full compact Specification Analysis Report, including findings with exact locations, FR-001..008 coverage/task IDs, metrics and next actions. Do not edit any file or fix anything. Do not invent findings; a clean audit should say so. No hooks/extensions are configured.