-
Notifications
You must be signed in to change notification settings - Fork 9
Fix/edit/rework planning and workflow classification CT-59 CT-104 #953
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Added new workflow classification system with three core workflows: - FIX: Address bugs without changing spec or schema - EDIT: Update functionality while preserving core schema - REWORK: Create new functionality with potentially new schema Implemented: - Intent classification using LLM - Plan generation based on workflow type - Preview integration in SpecPreview component - Workflow toggle UI in preview panel - Basic test coverage 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Fix imports in charm/src/imagine.ts - Fix CharmDetailView to use correct components - Update the SpecPreview component to use basic preview without workflow controls for now - Add proper fallbacks for LLM failures in tests 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Add current implementation status section - Document integration with existing functionality - Add implementation details for each component - Outline next steps for further development 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
When a user mentions any charm (except the implicit reference to the current charm), we must use the "rework" workflow which: 1. Constructs an argument cell that can access data from all referenced charms 2. Builds a combined schema from all references 3. Uses castNewRecipe instead of iterate This change: - Updates classifyIntent to automatically classify as "rework" when references exist - Adds a check in generateWorkflowPreview to override user workflow selection - Updates IMAGINE-DESIGN.md with detailed explanation of the reference handling - Adds skeleton tests for the reference handling behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
6a35590 to
50b8ec3
Compare
Next up: bug squashing
|
|
||
| // XML tag functions have been moved elsewhere | ||
| // Tests will be updated when we create proper tests for the workflow module |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wat?
| For IMAGINE workflows you MUST include both <result_schema> tags with valid JSON schemas. | ||
| Each schema must be a JSON object with "type": "object" and must include a "properties" object with property definitions. | ||
| Example schema format: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll move the schema to the second step in a later PR
| } | ||
|
|
||
| // For rework workflows, extract both argument and result schemas | ||
| if (workflowType === "imagine") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kinda messy logic, needs a cleanup
Todo
currentcharmformworkflow.tsContext