How this command is triggered — by the user, by Claude, or both
Slash command
/scope-pipeline:apiopusThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Launch the scope-api agent to create comprehensive API specifications from planning documents.
This agent will:
1. Read all documentation in `.claude/scope/{feature-name}/` starting with `plan.md`
2. Identify all required API endpoints and operations
3. Design RESTful endpoints with proper HTTP methods
4. Create request/response schemas with type definitions
5. Document authentication and authorization requirements
6. Design server-side functions and route handlers
7. Include error handling and status codes
8. Add frontend usage examples
9. Save to `.claude/scope/{feature-name}/api-spec.m...Launch the scope-api agent to create comprehensive API specifications from planning documents.
This agent will:
.claude/scope/{feature-name}/ starting with plan.md.claude/scope/{feature-name}/api-spec.mdUse this command when:
/scope-pipeline:plan phase and need API designThe agent creates comprehensive API documentation following REST best practices:
Recommended workflow:
/scope-pipeline:plan - Create the implementation plan/scope-pipeline:db - Design the database schema/scope-pipeline:api - Design API endpoints/scope-pipeline:ui - Visualize the UI/UX layouts/scope-pipeline:edge - Identify edge cases/scope-pipeline:test - Create test plan/scope-pipeline:task - Break down into tasks/scope-pipeline:exec - Execute implementation$ARGUMENTS
npx claudepluginhub andrewex/claude-marketplace --plugin scope-pipeline/api-docsGenerates OpenAPI 3.1 spec and Postman collection from plan.md API contracts. Auto-detects framework, validates spec-implementation consistency, outputs publishable docs.
/designDesigns RESTful or GraphQL APIs for a feature, generating OpenAPI 3.0 specs or GraphQL schemas with endpoints and request/response models. Also supports --graphql and --from-db flags.
/specGenerates feature specs via step-by-step dialogue: requirements.md (EARS notation), design.md (diagrams/TS interfaces), tasks.md (tasks/best practices).
/api-designApplies contract-first API design guidelines to specified endpoints or services, producing stable, evolvable interface contracts.
/apiDesigns, implements, and applies best practices for REST or GraphQL APIs based on a required requirement and optional API type (rest or graphql).