Workflow step decisions
SkillProductivityRecord the current workflow step decision through the task-bound Office CLI.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Workflow step decisions skill
What this skill tells your AI
The instructions your AI receives, as published by kdlbs/kandev in apps/backend/internal/office/configloader/skills/kandev-step-decision/SKILL.md and read by ahel’s review.
Use the task-bound CLI command when you hold the current review or approval seat and the run prompt advertises the decision action.
Record the decision
The only accepted verdicts are approved and rejected. Use a non-empty reason
that explains the evidence for the verdict.
$KANDEV_CLI kandev task decision --decision approved --reason "..."
Use approved as shown, or replace it with rejected when rejecting. Replace
the reason with the evidence for the current workflow step. Make this command
the final action for the turn, then stop. A repeated
decision supersedes the previous decision for that participant and step.
The command returns structured JSON with these fields:
{
"decision": "approved",
"role": "reviewer",
"step_id": "step-1",
"decision_id": "decision-1",
"decided_at": "2026-01-01T00:00:00Z",
"transition_applied": false,
"guards": []
}
Posting comments do not count as a workflow step decision. Approval-inbox commands do not count either. Do not use either operation instead of the task decision command.
Signals
- GitHub stars
- 771
- Forks
- 114
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
kandev-step-decision- Source
- github.com/kdlbs/kandev