Create requirements and scoped work items in Taskman, from product direction to an epic, feature or task.
Scanned 9/22/2026
Install to Claude Code
npx -y skills add vkroz/taskman --skill define --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Define?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vkroz-define)More formats (shields.io, HTML) on the badges page.
---
name: define
description: Create requirements and scoped work items in Taskman, from product direction to an epic, feature or task.
---
Arguments: `[product|epic|feature|task]`.
Read [the shared workflow](../../references/workflow.md) for CLI syntax, context, journals and closure rules.
Establish the intended outcome, scope, observable acceptance criteria and meaningful quality gates from the user's request and repository context. Ask only about unresolved decisions that affect the outcome. For a bug, include reproduction, expected and actual behavior; create it as type `task`.
For product work, update the project's existing vision, requirements or specification documents. For an epic or feature, create the parent and the minimum useful decomposition. For a single task, create only that task. Use `--parent` for hierarchy; do not invent separate slug-based links or mandatory tiers.
Read [composition guidance](../../rules/task-composition.md) when drafting work items. Persist with `new --body-file ... --json`, then set actual dependencies. Finalize items whose scope is agreed; leave unresolved questions visible in drafts. Return the created IDs and the outcome they describe. Definition does not authorize implementation.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!