feat: add issue-only Improve Kandev workflow (#1994)
This commit is contained in:
@@ -112,6 +112,16 @@ session to a lower-cost implementation model. Detailed feature, fix,
|
||||
validation, and delegation routing lives in the relevant skills, especially
|
||||
`planner-orchestration`.
|
||||
|
||||
Workflow-generated phase text such as `[IMPROVE PHASE]`, "implement the
|
||||
requested change", TDD checklists, verification commands, or commit steps does
|
||||
not opt a feature or behavior-changing fix out of spec-driven development. If
|
||||
the request does not reference an approved spec, plan, and task file, run
|
||||
`spec-driven-development` through the plan/task checkpoint and stop before
|
||||
production or permanent test changes. Continue directly to implementation only
|
||||
when approved task artifacts already exist, or when the user explicitly says
|
||||
to skip planning; a generic implementation envelope is not that explicit
|
||||
opt-out.
|
||||
|
||||
### Kandev Task Creation
|
||||
|
||||
Use Kandev task/session MCP APIs only when the user explicitly asks to create or
|
||||
@@ -167,4 +177,4 @@ For developing in ephemeral cloud VMs (Cursor Cloud, Codex, GitHub Codespaces, e
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2026-07-21
|
||||
**Last Updated**: 2026-07-27
|
||||
|
||||
Reference in New Issue
Block a user