agentic-sdd-research-speclisted

# Agentic SDD Research Spec Use this skill when a user asks for a spec-driven development document, a gap analysis against an SDD workflow, or an upgrade of a rough project draft into a high-quality planning artifact. The goal is a better specification, not implementation. ## Operating Rules - Treat the spec as the source of truth. Do not start coding unless the user explicitly asks for implementation. - Read local source material first, then use Exa advanced search to validate gaps, current terminology, and official behavior. - Prefer official documentation, primary project docs, standards, and maintained repositories over generic posts. - Separate stable product intent from technical choices. Keep "what and why" in the spec, and "how" in the plan. - Add explicit verification criteria. A task is not complete unless the validation command or observable result is defined. - Flag unresolved ambiguity as an open question or clarification marker; do not silently invent risky requirements. - Keep outputs actionable for agents: exact file paths, commands, phase gates, acceptance criteria, and stop conditions. - Preserve the user's goal. Improve accuracy, structure, and completeness without expanding into a different product. ## Workflow 1. **Source Intake** - Read the user's existing draft, SDD guide, README, and repository structure. - Identify the target artifact type: spec, plan, tasks, README, verification spec, or gap report. - Note constraints such as "docs only