Considerations over custom task states

[alioshr]

Are you considering allowing to configure custom states? When something is done it can only be set to "done", but as in PM tools, we can have more intermediary states, such as "to be tested", "tested", etc. This would allow enforcing CC for instance to spawn a testing agent to review the code, etc. My workaround now is to use a PreToolUse hook so the agent tells the main agent to invoke another agent to review before marking as complete.

Not sure if review etc is intended to be used in a different way. Templates do not enforce so I would not rely on them.

[jpicklyk]

@alioshr yes. The main branch has already moved to that concept essentially. You can check the status-workflow-config.yaml to see how you can define your own workflow. The code has moved away from Templates as they are too ridged and have other limitations.

[jpicklyk]

@alioshr the latest release fully supports what you are desiring. You can now build your hooks off of Role transitions to be more specific when a WorkItem moves from work -> review stage. You can see some examples of such things with the current claude plugin hooks I have for the project.

The Hook is how you enforce the action, it's the correct approach for Claude at least.