Menu
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
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.
Based on SOC occupation classification
| 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.