npx claudepluginhub javimontano/jm-adk-alfaGenerate a detailed functional specification document covering requirements, user stories, acceptance criteria, and technical constraints. Use this to formally document what the system must do.
input — Requirements source or document path (required)format — Spec format: ieee | agile | lean (optional, default: agile)detail — Detail level: high-level | detailed | exhaustive (optional, default: detailed)/jm-adk:spec input="Customer portal with self-service features"
/jm-adk:spec input=./docs/requirements.md format=agile detail=exhaustive
/jm-adk:analyze — Full analysis pipeline/jm-adk:requirements — Extract requirements/jm-adk:brief — Shorter technical brief/specAuthors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.
/specGenerates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.
/specGenerates feature specs via step-by-step dialogue: requirements.md (EARS notation), design.md (diagrams/TS interfaces), tasks.md (tasks/best practices).
/specInitiates phased Spec Mode for a feature description: interactively refines requirements (EARS), designs (Mermaid, TS interfaces), and tasks, generating requirements.md, design.md, tasks.md.