Menu
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Propose a safe rollout/migration plan with monitoring and rollback steps.
Produce a clear, review-ready SDD specification skeleton in Markdown.
| name | mcp-integration |
| description | Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec. |
Add a focused MCP integration section to an existing spec.
Extend this spec with an “MCP Integration” section.
Include:
- What MCP server/tooling is needed and why
- Inputs/outputs (schemas, fields)
- AuthN/AuthZ and audit requirements
- Error handling and retries
- Rate limits/timeouts
- Observability (logs/metrics)
- Test approach (mocked vs real)
Keep it concise.