Skip to content
Agentmart
Submit a tool

task-workflow

Operate the Orca task system on GitHub — task issues, workflow labels, the project board, and dispatching work to a worktree+agent.

Skill by JAGUARAVI

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying task-workflow?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jaguaravi-task-workflow

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Operate the Orca task system on GitHub — task issues, workflow labels, the project board, and dispatching work to a worktree+agent. Use when asked to "pick up a task", "what's ready", "start a task", "dispatch P0-12", "close the task", "update the board", "create issues", or "sync task labels". Do not use for landing/merging PRs (that is `merge-agent`).

Use cases: productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/task-workflow

What's inside

Skill name
task-workflow
Description
Operate the Orca task system on GitHub — task issues, workflow labels, the project board, and dispatching work to a worktree+agent. Use when asked to "pick up a task", "what's ready", "start a task", "dispatch P0-12", "close the task", "update the board", "create issues", or "sync task labels". Do not use for landing/merging PRs (that is `merge-agent`).
License
MIT
Instructions
50 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • files: referenced but missing: templates/TASK-BRIEF.md

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Task workflow

One task = one issue = one worktree = one agent = one PR. This skill drives that loop.

## Read the plan
- Index: `docs/tasks/README.md` (table: `ID | Task | Depends on | Owns (may edit) | Agent fit`).
- Brief: `docs/tasks/<PHASE>/<ID>-<slug>.md` (follows `templates/TASK-BRIEF.md`).

The **Owns** column is the contract: only edit the listed paths. If two tasks share a path, they
must not run in the same wave.

## Lifecycle
```
ready ──start──► in-progress ──PR open──► review ──merge──► closed (Done)
  ▲
  └─ blocked ──(all dependency issues closed)──► ready
```

## Commands
```bash
task status                       # ready / in-progress / review / blocked
task next --phase P1 --n 3        # the next unblocked tasks
task start P1-08 --agent claude   # worktree + agent + issue, label in-progress
task done  P1-08                  # close after the PR merges
task sync                         # reconcile labels from issue/PR state now
```

Dispatch without the CLI:
```bash
orca-dispatch P1-08 --agent claude   # brief -> Orca worktree + agent prompt
```

## Creating the issues (once per repo / when the plan changes)
```bash
github/deps-from-index.py docs/tasks/README.md -o docs/tasks/deps.json
github/setup-issues.sh <owner/repo> --deps docs/tasks/deps.json --phases P0 P1 P2 --gh <Name>-gh
```

## Rules an agent must follow
- **Do not merge your own PR.** Implement, label `merge-ready`, stop.
- **Respect `Owned paths`.** No opportunistic edits elsewhere; a shared path change needs its own PR.
- **Freeze interfaces.** After the contracts task lands, a change to it is its own PR.
- **Human gates (⛩) block.** Do not start a gated task until the sign-off lands on the issue/PR.
- **Keep dependencies honest.** The index table is the single source of truth; never hand-edit
  `deps.json` — regenerate it.

## Definition of Done before `merge-ready`
acceptance criteria pass · tests added · docs/ADR updated · linters + CI green · scope matches the
brief · no frozen paths touched · linked issue updated.

From JAGUARAVI/orca-kit, MIT.

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Oct 13, 2026 (17 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JAGUARAVI

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get task-workflow running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying task-workflow?

CallGet help
Cite this page

task-workflow skill. Agent Mart. https://agentmart.dev/skills/jaguaravi-task-workflow (last updated 2026-10-24)