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.
Install
$ agentstack add skill-danielc000-loom-task-start ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-danielc000-loom-task-start) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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
- Find or create the task —
tasks_list(theloom-tasksMCP); 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".
- 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.
- Move it — set the task to the
activecolumn (the in-progress ROLE) viatasks_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.
- Load context before changing anything —
git log --oneline -15, readCLAUDE.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
- Source: DanielC000/loom
- License: MIT
- Homepage: https://danielc000.github.io/loom/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.