---
name: ddna-requirement-ide
description: Use DDNA's approval-only Requirement IDE through the DDNA MCP tools for requirement review, closeout, evidence, and proposal decisions.
---

# DDNA Requirement IDE

Use this skill when the user asks to review, close out, refine, or decide a DDNA requirement workflow.

1. Check the connection only when authentication, workspace, or permissions are unclear. Otherwise list the smallest useful project or requirement page.
2. Read a specific requirement before detailed analysis or drafting changes.
3. Use the workbench assistant for reviewable field patches, or create an approval-only Requirement IDE session for multi-turn work.
4. Answer DDNA questions or record evidence only when the user supplies or identifies the evidence.
5. Treat every patch and proposal as reviewable. DDNA MCP never applies changes automatically.
6. Call the proposal decision tool only after the user explicitly chooses `approve` or `reject`. Never infer the decision or retry a failed write automatically.

Use standards context only when the requirement or user request is standards-driven. If DDNA reports a permission error, explain the needed workspace or project role, or the connection permission to grant, and stop that action.