caddis-plugin: Instructions file for GitHub Copilot

Plan Mode Instructions

These instructions apply when the user enters "plan mode", "requirements mode", or provides raw requirements that need analysis before implementation.

Trigger Conditions

Activate plan mode when the user:

• Says "plan mode", "planning mode", or "requirements mode"
• Says "I need to build...", "We need a system that...", "Create a project for..."
• Provides vague or high-level requirements
• Asks for help with a new feature without specific details
• Says "help me understand what we need"

Plan Mode Behavior

DO NOT

• ❌ Write code immediately
• ❌ Make assumptions about requirements
• ❌ Skip the clarification phase
• ❌ Provide implementation details before understanding the problem
• ❌ Generate files without user confirmation

DO

• ✅ Ask clarifying questions first
• ✅ Confirm understanding before proceeding
• ✅ Break down complex requirements into components
• ✅ Identify missing information
• ✅ Propose a plan before execution
• ✅ Wait for user approval at each phase

Documentation Metadata

Any PRD, plan, requirements doc, or other descriptive Markdown artefact created or updated during plan mode must follow .github/instructions/document-frontmatter.instructions.md.

Plan Mode Workflow

Phase 1: Discovery (Required)

When user provides requirements, respond with:

I'm in plan mode. Before we start building, let me understand the requirements fully.

**What I understood:**
{summarize what you understood}

**Questions I need answered:**
1. {specific question about scope}
2. {specific question about users}
3. {specific question about data}
4. {specific question about constraints}

**Missing information:**
- {what's not clear}

Please answer these questions, or let me know if my understanding is correct.

Phase 2: Confirmation

After gathering information:

**Requirements Summary:**

| Aspect | Details |
|--------|---------|
| Goal | {one sentence} |
| Users | {who will use this} |
| Data Sources | {where data comes from} |
| Key Features | {main capabilities} |
| Constraints | {timeline, tech, compliance} |

**Proposed Approach:**
1. {step 1}
2. {step 2}
3. {step 3}

**Recommended Agents:**
- PRD agent - To generate formal PRD
- Architect agent - To design the system
- Implement (or other relevant) agent - For implementation

Does this look correct? Should I proceed with generating the PRD?