Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

eroveda

@eroveda source repo

9 published skills

  1. ▌
    Swebok Decompose · eroveda
    Breaks down a project description into IEEE SWEBOK-categorized work nodes. Use after universal-framework (or directly for straightforward projects) to create the work breakdown. Do NOT use for documentation generation or spec creation — those have their own skills. Trigger with "decompose this project", "break down using SWEBOK", or "create work breakdown".
    0
    installs
  2. ▌
    Generate User Guide · eroveda
    Creates USER_GUIDE.md for end-users (not developers). Use when preparing onboarding material or end-user documentation. Do NOT use for API docs (use generate-api-catalog) or technical architecture (use generate-architecture-doc). Trigger with "generate user guide", "document for end users", or "create USER_GUIDE.md".
    0
    installs
  3. ▌
    Universal Framework · eroveda
    Applies the INPUTS → PROCESOS (Processes) → OUTPUTS → SOPORTE (Support) framework to ANY software type. Use as the FIRST step when decomposing any project, especially non-standard types (IoT, ML, blockchain, simulation, etc.). Do NOT use for projects already decomposed or when the user only needs documentation. Trigger with "apply universal framework", "decompose using INPUTS-PROCESOS-OUTPUTS", or "what are the dimensions of this project".
    0
    installs
  4. ▌
    Generate API Catalog · eroveda
    Creates API_CATALOG.md or INTERFACE_CATALOG.md documenting all system interfaces with examples. Use when documenting APIs, CLIs, SDKs, or message interfaces for consumers (frontend devs, integrators, partners). Do NOT use for architecture overview (use generate-architecture-doc) or user-facing docs (use generate-user-guide). Trigger with "generate API catalog", "document the API", or "create interface catalog".
    0
    installs
  5. ▌
    Swebok Generate Spec · eroveda
    Converts a SWEBOK node into a complete executable specification. Use after swebok-decompose to generate detailed specs ready for code generation by any AI agent. Do NOT use for documentation — use the generate-* skills for that. Trigger with "generate spec for this node", "create executable specification", or "spec this node".
    0
    installs
  6. ▌
    Generate Architecture Doc · eroveda
    Generates ARCHITECTURE.md following IEEE 15289 standards. Use when documenting a new or existing project's technical architecture. Do NOT use for user-facing docs (use generate-user-guide) or API docs (use generate-api-catalog). Trigger with "generate architecture doc", "document the architecture", or "create ARCHITECTURE.md".
    0
    installs
  7. ▌
    Generate Functional Flows · eroveda
    Creates FUNCTIONAL_FLOWS.md describing user-facing flows in plain language. Use when documenting for non-technical stakeholders (managers, PMs, clients). Do NOT use for technical architecture (use generate-architecture-doc) or API docs (use generate-api-catalog). Trigger with "generate functional flows", "document user flows", or "create FUNCTIONAL_FLOWS.md".
    0
    installs
  8. ▌
    Generate Testing Strategy · eroveda
    Generates TESTING_STRATEGY.md — a consolidated testing strategy document that aggregates the acceptance criteria from all executable specs into a global testing approach (unit, integration, E2E, load, security). Use this skill AFTER swebok-generate-spec has produced 03-SPECS.yaml (or the specs/ directory). ## When to invoke this skill - After all specs have been generated - When the user asks for a "testing strategy", "QA plan", "test plan", or "TESTING_STRATEGY.md" - When planning the testing phase of a project ## When NOT to invoke - Before specs exist - For projects without acceptance criteria defined
    0
    installs
  9. ▌
    Generate Blueprint Summary · eroveda
    Use this skill AFTER all other Blueprint skills have generated their outputs. Produces BLUEPRINT.md — a master index document that ties together all the project blueprint files (analysis, decomposition, specs, architecture, flows, user guide, API catalog). This is the "table of contents" or "dashboard" of the project blueprint. It's the first file someone should open when arriving at the project. ## When to invoke this skill - After running the Stage 1 skills (universal-framework, swebok-decompose, swebok-generate-spec) - After running the Stage 2 documentation skills (architecture-doc, functional-flows, user-guide, api-catalog) - When the user asks for a "project summary", "blueprint dashboard", "table of contents", or "BLUEPRINT.md" ## When NOT to invoke - Before other skills have generated their outputs - For projects without complete blueprint generation
    0
    installs