Spaces:
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
@WorkPackageName [mode] user instruction
Supported modes:
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
- Test case generation
- Automation test script generation
- Mock user information reading
- 2D design brief / image prompt generation
- Certification plan generation
- Patent check topic generation
- Design FMEA generation
- Hardware BOM / Software SBOM / Feature List generation
- Quality Gate questionnaire generation
Simulated Output Format
{
"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:
@Final Engineering Concept execute Generate BOM and SBOM.
Output:
{
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.