Install any skill in seconds. Free to start, no credit card required.
Get Started Free →1mancompany/task_lifecycle
Task lifecycle state machine — states, transitions, and task tree model.
Passed 21 of 21 test cases with the skill, and 11 of 21 without it.
and 11 more in the full report
11 fixed11 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
A team lead is reviewing a subtask submission and notices missing test coverage. What system function must the lead execute to formally reject the child item?
| Checked | Without skill | With skill |
|---|---|---|
| Names reject_child as the method used to reject a child task. | Missed | Passed |
The instructions your model reads when the skill loads.
Every task in the system follows this state machine:
| State | Meaning |
|---|---|
| pending | Created, waiting to be processed |
| processing | Actively being executed by an employee |
| holding | Waiting for subtasks to complete or external input |
| completed | Employee finished execution, awaiting supervisor review |
| accepted | Supervisor approved the deliverable |
| finished | Fully done, archived |
| failed | Execution failed or supervisor rejected |
| blocked | Dependency task failed, cannot proceed |
| cancelled | Cancelled |
State flow: pending → processing → completed → accepted → finished ↕ holding (pause/resume) completed → failed (rejection) → processing (retry)
Key distinctions:
Task tree model:
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.