← ClaudeAtlas

taskforgelisted

The primary entry point for the taskforge engineering workflow - create and import tasks, query and manage the backlog, route work, and unblock humans. Use whenever the user wants to add or import work ("add a task", "import issue
hashirventhodi/taskforge-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill hashirventhodi/taskforge-skills
# taskforge The primary entry point of the taskforge workflow, and its shared SDK: contracts, the deterministic engine, templates, and the reviewer component. This skill **creates, queries, routes, and maintains** tasks; it never refines, decides, or implements — those are `taskforge-refine`, `taskforge-explore`, and `taskforge-run`. Read `CONTRACTS.md` (sibling file) once per session before any taskforge work. Resolve the engine per its "Locating the engine" section; below, `$SCRIPT` means that resolved path. ## The workflow in one paragraph Every piece of work is a durable Task in `.tasks/`. Tasks route by **derived readiness**: no active specification → `taskforge-refine` (the universal entry point: adopt / elaborate / clarify / escalate); a pending escalation → `taskforge-explore` (decisions, optional decomposition into children); an active spec and no blockers → `taskforge-run` (implement + independent fresh-context review). Skills reason and emit results; the engine applies them — versioning, cascades, relationships, budgets, readiness. Nothing is auto-executed. ## Commands Dispatch on the user's intent (or the argument after `/taskforge`). Every command reports per `references/reporting.md` and **stops** — routing names the next skill; it never runs it. | command | intent | how | |---|---|---| | *(none)* / `status` | overview | `list`; summarize counts per readiness, surface `blocked_on_human` tasks with their questions | | `add <source…>` | create/import tasks