new-task

SkillProductivity

Start a Quantick GitHub issue in its required branch and worktree.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the new-task skill

What this skill tells your AI

The instructions your AI receives, as published by milocaetano/quantick in .agents/skills/new-task/SKILL.md and read by ahel’s review.

Campaign children override the main-based examples via the integration contract, including review keys.

Start work on an issue

Argument: the issue number (e.g. /new-task 3). If missing, list open issues in the current milestone (gh issue list --milestone "v0.1 - Engine core") and ask which one to pick.

Steps

  1. Read the issue: gh issue view <N>. If it does not exist or is already closed, stop and report. Summarize scope and acceptance criteria back to the user — they become the work checklist.

  2. Guard against duplicates: check git worktree list and git branch --list '<prefix>/<slug>'. If a worktree or branch for this issue already exists, switch into it and report — never create a second one for the same issue.

  3. Create a worktree from updated main — one goal, one worktree (see CLAUDE.md). Never check the branch out in the main clone; parallel agents must never share a working tree:

    git fetch origin
    git worktree add -b <prefix>/<short-kebab-slug> ../quantick-worktrees/<prefix>-<short-kebab-slug> origin/main
    cd ../quantick-worktrees/<prefix>-<short-kebab-slug> && cargo build -p quantick-guards
    

    Then work from inside ../quantick-worktrees/<prefix>-<short-kebab-slug>. That cargo build arms guard-watch, which reports nothing — not "clean", nothing — until the binary exists; CLAUDE.md's Verification loop owns why. A branch started here is exactly the one that would otherwise miss it, since the arming rule used to live only in mission step 6.

    Prefix from the issue's labels: bug or type:fixfix/, type:docsdocs/, everything else → feat/. Slug: short kebab-case from the issue title.

  4. Move the board card to In Progress (project "quantick roadmap"):

    ITEM=$(gh project item-list 1 --owner milocaetano --format json \
      --jq '.items[] | select(.content.number==<N>) | .id')
    # If empty, the issue is not on the board yet - add it first:
    # ITEM=$(gh project item-add 1 --owner milocaetano --url <issue-url> --format json --jq '.id')
    gh project item-edit --id "$ITEM" --project-id PVT_kwHOA0fkv84BeK9c \
      --field-id PVTSSF_lAHOA0fkv84BeK9czhYnKUg --single-select-option-id 47fc9ee4
    
  5. Report: branch name, worktree path, card moved, and the acceptance criteria as a checklist. For area:engine issues, remind: test-first — fixture trades and expected bars are written before the implementation.

Board reference (project 1)

  • Project ID: PVT_kwHOA0fkv84BeK9c
  • Status field ID: PVTSSF_lAHOA0fkv84BeK9czhYnKUg
  • Status options: Todo f75ad846 · In Progress 47fc9ee4 · Done 98236657

Signals

GitHub stars
36
Forks
4
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
new-task-milocaetano
Source
github.com/milocaetano/quantick