Spaces:
Running
Running
| # 05 Reference Command and Execution Plan | |
| ## Goal | |
| Support a Cursor-like interaction pattern for product work packages. | |
| The user can reference a work package from chat and ask AI to reason about it, plan it, change it, or execute tasks inside it. | |
| ## Command Syntax | |
| ```text | |
| @WorkPackageName [mode] user instruction | |
| ``` | |
| Supported modes: | |
| ```text | |
| ask | |
| plan | |
| change | |
| execute | |
| ``` | |
| ## Mode Definitions | |
| ### ask | |
| Use when the user wants to ask a question about a selected work package. | |
| Behavior: send selected work package as context to LLM; answer in chat; do not update board. | |
| ### plan | |
| Use when the user wants AI to further break down a work package. | |
| Behavior: add/refine tasks, next steps, or deliverables. | |
| ### change | |
| Use when the user wants AI to directly modify a work package. | |
| Behavior: update selected work package and explain what changed. | |
| ### execute | |
| Use when user wants AI to perform a task inside a work package. | |
| MVP behavior: simulate execution, generate structured output, save output to selected work package, mark related task as done if appropriate, and show disclaimer. | |
| ## Supported Simulated Execution Types | |
| 1. Test case generation | |
| 2. Automation test script generation | |
| 3. Mock user information reading | |
| 4. 2D design brief / image prompt generation | |
| 5. Certification plan generation | |
| 6. Patent check topic generation | |
| 7. Design FMEA generation | |
| 8. Hardware BOM / Software SBOM / Feature List generation | |
| 9. Quality Gate questionnaire generation | |
| ## Simulated Output Format | |
| ```json | |
| { | |
| "title": "Simulated Output Title", | |
| "type": "table | text | checklist | code | design_brief | image_prompt | risk_table | bom | sbom | feature_list", | |
| "executionMode": "simulated", | |
| "disclaimer": "This is a simulated execution result generated for demo purposes. No real external tool, engineering review, certification approval, user database, image generation service, patent search, or test system was executed.", | |
| "content": "..." | |
| } | |
| ``` | |
| ## Command Parser Requirements | |
| Input: | |
| ```text | |
| @Final Engineering Concept execute Generate BOM and SBOM. | |
| ``` | |
| Output: | |
| ```ts | |
| { | |
| referencedPackageName: "Final Engineering Concept", | |
| mode: "execute", | |
| instruction: "Generate BOM and SBOM." | |
| } | |
| ``` | |
| ## Matching Rules | |
| Support exact title match, short name match, case-insensitive match, and trimmed spaces. | |
| Examples: | |
| - `@CRS` | |
| - `@SRS` | |
| - `@Design FMEA` | |
| - `@Service Review` | |
| - `@Final Engineering Concept` | |
| ## Error Handling | |
| If package is not found, ask user to select an existing package and show close matches if possible. | |
| If mode is missing, default to `ask`. | |