# Task Start

> Use when starting a new task, feature, bugfix, or refactor in a Loom project — "let's start", "new task", "working on", "implement", "begin". Ensures a board task exists with a clear scope and a sharp definition of done, then loads context before any code changes.

- **Type:** Skill
- **Install:** `agentstack add skill-danielc000-loom-task-start`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [DanielC000](https://agentstack.voostack.com/s/danielc000)
- **Installs:** 0
- **Category:** [Databases](https://agentstack.voostack.com/c/databases)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [DanielC000](https://github.com/DanielC000)
- **Source:** https://github.com/DanielC000/loom/tree/main/packages/daemon/assets/skills/task-start
- **Website:** https://danielc000.github.io/loom/

## Install

```sh
agentstack add skill-danielc000-loom-task-start
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Task Start (Loom)

Make the work trackable on the board before diving in. The board is the source of truth — one task =
one focused, independently-mergeable change.

## Steps

1. **Find or create the task** — `tasks_list` (the `loom-tasks` MCP); if none matches, `tasks_create`
   with a clear, specific title in **Conventional-Commits form** (`type(scope): summary` — lowercase
   type like `feat`/`fix`/`refactor`, imperative summary), drawing the scope from the project's
   `CLAUDE.md` "Commit scopes".
2. **Scope it.** Put the scope **and a sharp definition of done** in the task body (`tasks_update`
   body). The DoD states what *proves* it works — a command that exits clean, a manual repro, a
   regression check. A task without a DoD isn't ready to work. If an open decision blocks pinning the
   DoD, ask the human via `question_ask` (the Requests inbox) rather than guessing. Keep it to one
   logical change; if it's really several, split it.
3. **Move it** — set the task to the `active` column (the in-progress ROLE) via `tasks_update`
   columnKey. First, **skip any card flagged `held`** (an owner brake) **or `deferred`** (the manager
   hasn't sequenced it) — don't begin work on those.
4. **Load context before changing anything** — `git log --oneline -15`, read `CLAUDE.md`, and read
   the relevant code/notes so your change matches what's there. Reuse existing shapes over inventing
   new ones.

Then implement: keep the change small and matched to the surrounding code, meet the DoD, and build/
verify before reporting it done.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [DanielC000](https://github.com/DanielC000)
- **Source:** [DanielC000/loom](https://github.com/DanielC000/loom)
- **License:** MIT
- **Homepage:** https://danielc000.github.io/loom/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-danielc000-loom-task-start
- Seller: https://agentstack.voostack.com/s/danielc000
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.