antigravity-ipa-workflow/skills_index.json

{"skills":[
  {"name":"ipa-all","path":"skills/ipa-all/SKILL.md","description":"Run the full IPA documentation pipeline in sequence — spec, design, detail, validate. Use when you want to generate all IPA docs in one command, need a complete documentation pass for a project, or are a power user comfortable skipping individual validation gates. Trigger phrases: "generate all IPA docs", "full IPA pipeline", "run ipa all"."},
  {"name":"ipa-bd","path":"skills/ipa-bd/SKILL.md","description":"Generate UI_SPEC.md only from an existing SRD. Use when you need granular control over basic design generation, want to regenerate only the UI specification without touching the SRD, or are working on UI-only updates. Trigger phrases: "generate UI spec", "create basic design", "generate ui_spec only"."},
  {"name":"ipa-context-aware-planning","path":"skills/ipa-context-aware-planning/SKILL.md","description":"Extends planning with @path context syntax for design mockup integration and tech-stack-aware code generation. Use when planning with design file references, when a plan command includes @path arguments pointing to mockups or prototypes, or when tech-stack-specific code generation is needed. Trigger phrases: "plan with design context", "use @path in plan", "planning with mockups"."},
  {"name":"ipa-dd","path":"skills/ipa-dd/SKILL.md","description":"Alias for ipa-detail — generate API_SPEC.md and DB_DESIGN.md from SRD and UI_SPEC. Use when referring to the detail design stage by its legacy name, generating interface and data design specs, or completing Stage 3 of the IPA pipeline. Trigger phrases: "generate detail design", "create api spec and db design", "ipa dd"."},
  {"name":"ipa-design","path":"skills/ipa-design/SKILL.md","description":"Generate production-ready HTML/CSS/JS prototypes from UI_SPEC.md. Use when you need visual mockups for all screens defined in the UI spec, want to validate UI before proceeding to detail design, or need HTML prototypes for design analysis. Trigger phrases: "generate prototypes", "create html mockups", "generate ui prototypes from spec"."},
  {"name":"ipa-detail","path":"skills/ipa-detail/SKILL.md","description":"Generate API_SPEC.md and DB_DESIGN.md from SRD and UI_SPEC — Stage 3 of the IPA pipeline. Use when SRD and UI_SPEC are complete and interface contracts plus database schema need to be defined, when designing API endpoints from screen requirements, or when creating language-agnostic data models from entity lists. Trigger phrases: "generate api spec and db design", "ipa detail design", "stage 3 ipa"."},
  {"name":"ipa-docs-split","path":"skills/ipa-docs-split/SKILL.md","description":"Split large IPA documentation files into modular folder structures when they exceed 500 lines. Use when an IPA doc becomes too large to navigate efficiently, when splitting API_SPEC, DB_DESIGN, or SRD into domain-based modules, or when docs exceed 500 lines. Trigger phrases: "split large ipa doc", "modularize api spec", "split docs into folders"."},
  {"name":"ipa-docs-sync","path":"skills/ipa-docs-sync/SKILL.md","description":"Sync IPA docs (API_SPEC, DB_DESIGN, UI_SPEC) with actual codebase implementation after coding is complete. Use after finishing backend tasks, when endpoint or schema drift has occurred, or to mark endpoints as implemented. Trigger phrases: "sync docs after coding", "update api spec from code", "ipa docs sync"."},
  {"name":"ipa-docs","path":"skills/ipa-docs/SKILL.md","description":"IPA documentation sync specialist — tracks implementation status with symbols (pending/done/synced) across API_SPEC, DB_DESIGN, and UI_SPEC. Use when syncing docs after code implementation, verifying endpoint coverage, or keeping IPA docs accurate without full regeneration. Trigger phrases: "sync ipa docs", "update api spec after coding", "sync docs with implementation"."},
  {"name":"ipa-fast","path":"skills/ipa-fast/SKILL.md","description":"Run the complete IPA workflow in one command with minimal prompts, skipping all validation gates. Use when experienced with IPA and project scope is well understood, for rapid prototyping with a known requirement, or when combining raw text, URL, and image references in one pass. Trigger phrases: "ipa fast mode", "full ipa in one command", "skip all gates and generate everything"."},
  {"name":"ipa-help","path":"skills/ipa-help/SKILL.md","description":"Display the IPA workflow quick reference cheatsheet with commands, warnings, tips, and workflow paths. Use when you need a summary of available IPA commands, want to understand the full pipeline at a glance, or need to share workflow guidance. Trigger phrases: "ipa help", "show ipa commands", "ipa cheatsheet"."},
  {"name":"ipa-import","path":"skills/ipa-import/SKILL.md","description":"Import external requirements documents (SRS, PRD, research reports) into the IPA documentation structure with proper IDs and traceability. Use when converting external specs from Gemini Deep Research, Perplexity, or manually written SRS files into IPA format. Trigger phrases: "import external srs", "convert requirements to ipa", "import requirements document"."},
  {"name":"ipa-init","path":"skills/ipa-init/SKILL.md","description":"Initialize IPA documentation by reverse-engineering an existing codebase that has no docs. Use when applying the IPA workflow to a running project, extracting API routes and DB schema from code, or generating a documentation baseline for legacy systems. Trigger phrases: "extract docs from code", "initialize ipa for existing project", "reverse engineer ipa docs"."},
  {"name":"ipa-mockup-analyze","path":"skills/ipa-mockup-analyze/SKILL.md","description":"Extract design specifications from HTML mockups using AI vision and CSS parsing to generate a UI_DESIGN_SPEC.md with design tokens, component mapping, and responsive specs. Use when converting visual prototypes into implementation-ready specs, analyzing HTML mockups for design system extraction, or preparing tech-stack-specific component mappings. Trigger phrases: "analyze html mockups", "extract design tokens from prototypes", "generate ui design spec from mockups"."},
  {"name":"ipa-planner","path":"skills/ipa-planner/SKILL.md","description":"IPA-aware planning that enriches implementation plans with traceability references (FR-xx, S-xx, E-xx), TDD detection for logic-heavy tasks, and design context from @path mockup references. Use when creating plans in projects with IPA docs, when tasks need to reference SRD features and API specs, or when design mockups should inform implementation tasks. Trigger phrases: "create ipa plan", "plan with traceability", "ipa-aware implementation plan"."},
  {"name":"ipa-spec","path":"skills/ipa-spec/SKILL.md","description":"Generate SRD.md and UI_SPEC.md with design research — Stage 1 of the IPA pipeline. Use when starting a new project or feature that needs structured requirements and UI specification, when converting raw ideas into formal docs, or when combining text, URL, and image inputs into a full spec. Trigger phrases: "generate srd and ui spec", "create ipa spec", "stage 1 ipa specification"."},
  {"name":"ipa-srd","path":"skills/ipa-srd/SKILL.md","description":"Generate SRD.md only — the System Requirement Definition following IPA standard with 15 sections. Use when granular control over requirement generation is needed, when only the SRD needs to be regenerated without touching UI_SPEC, or when working as a Business Analyst generating structured requirements. Trigger phrases: "generate srd only", "create system requirement definition", "generate srd without ui spec"."},
  {"name":"ipa-start","path":"skills/ipa-start/SKILL.md","description":"Interactive wizard that guides users through selecting the correct IPA workflow path based on their project situation. Use when starting the IPA process for the first time, when unsure which IPA command to run first, or when onboarding to the workflow. Trigger phrases: "start ipa workflow", "ipa wizard", "help me start ipa"."},
  {"name":"ipa-validate","path":"skills/ipa-validate/SKILL.md","description":"Validate IPA documentation consistency, traceability, and completeness — checks ID cross-references, coverage gaps, and gate status across all four IPA docs. Use after manually editing docs, before planning, or after running ipa-docs-sync to verify completeness. Trigger phrases: "validate ipa docs", "check ipa traceability", "run ipa validation"."},
  {"name":"ipa-validator","path":"skills/ipa-validator/SKILL.md","description":"Core IPA validation engine — checks documentation consistency, ID cross-references, and traceability chain across SRD, UI_SPEC, API_SPEC, and DB_DESIGN. Activated automatically by ipa-validate, ipa-all, and ipa-init. Trigger phrases: "validate ipa documentation", "check id consistency", "ipa traceability check"."},
  {"name":"lean-analyst","path":"skills/lean-analyst/SKILL.md","description":"Lean Software Development methodology framework — provides MVP definition criteria, feature prioritization matrix, assumption validation methods, and phase breakdown rules. Activated automatically by lean, lean-user-research, and lean-analyze-usage. Trigger phrases: "lean methodology", "mvp framework", "feature prioritization lean"."},
  {"name":"lean-analyze-usage","path":"skills/lean-analyze-usage/SKILL.md","description":"Analyze post-launch usage data to generate improvement recommendations with prioritized action items. Use after a product has launched and usage data is available, when identifying feature adoption gaps or funnel drop-offs, or when planning the next iteration based on real user behavior. Trigger phrases: "analyze usage data", "post-launch analysis", "lean usage analysis"."},
  {"name":"lean-user-research","path":"skills/lean-user-research/SKILL.md","description":"Generate user research documentation — personas, customer journey maps, and competitor landscape — before MVP definition. Runs BEFORE lean and IPA stages. Use when defining target users and their pain points, mapping the customer journey to inform UI design, or researching competitors before committing to an MVP scope. Trigger phrases: "user research", "create personas", "customer journey map"."},
  {"name":"lean","path":"skills/lean/SKILL.md","description":"Lean Software Development analysis — defines MVP scope for new projects or analyzes improvement opportunities for existing ones. Runs BEFORE IPA stages. Use when starting a new idea that needs MVP definition and scope validation, when analyzing a feature improvement against an existing system, or when eliminating waste before committing to full IPA documentation. Trigger phrases: "lean analysis", "define mvp", "lean feature analysis"."}
]}