Ability to 'out of flow' create a design/task doc

[chrisns]

I keep finding that if I confuse cc too much (likely exhausting context) by iterating lots on the requirements or design phase it then forgets the next phase its meant to do, resulting in it not using the right subagent and then incorrectly formatted and not-comprehensive subsequent docs.

It'd be great to ideally use clickable tool tips in the same way the "Start Task" work so that the placeholder

<!-- kiro-spec: mcp-interface-improvements/design -->
# Design Document

This document has not been created yet.

Please approve the requirements document first.

Has a button i can click to approve the previous phase doc and create this one.

[notdp]

200k context and sub-agents are mostly sufficient to complete a spec process. If Claude Code forgets the process, you can manually use @spec-system-prompt-loader and tell it which stage of the process you are in and which spec folder needs to be completed.

[chrisns]

could you possibly suggest a prompt that might work for that? 🙏

a button to do that would be awesomes ;)

Happy to do the work and raise the PR if you agree?

I'll work to understand the code with how you're doing the Start Task clickable to do the same for an empty design+tasks doc

[notdp]

@spec-system-prompt-loader and tell it which stage of the process you are in and which spec folder needs to be completed.

eg:
@spec-system-prompt-loader 
load the spec workflow
I am in the design phase, and we are working on the spec: .claude/spec/{spec-name}/
Please continue your design work.

There is no specific format, just tell Claude code the information it needs. When it doesn't work, manually @ the corresponding agent.