Guides

Task workflow

How mallard's skills chain on one task, from the brief to the merge request, and which step owns what.

Mallard's skills are built to be used in a sequence. Each step is a skill you start, and each skill ends with a Next: line that points to the following one. Nothing runs the chain for you: every commit, push, merge request, time entry or client message waits for your OK.

The chain works on any stack mallard covers: PrestaShop, Laravel, plain PHP or JS. Stack-specific steps live inside each skill.

The chain

/task <id>          brief + branch + type
  |
  |-- brief thin or unclear?    grill
  v
route by type       bug -> diagnose-bug
                    translation, image, layout, security -> the skill or agent /task names
  v
verify              verify-ps-project (PrestaShop), the project's own tests (Laravel)
                    blast-radius when shared code changed
  v
task-review         diff vs brief and AGENTS.md, read-only
  v
mr-flow             branch, commit, push, merge request
  v
/task done <id>     log time
  v
reflect             turn repeated mistakes into skill edits

What each step does

StepSkillWhat it does
Brief/task (task-context)Fetches the task, builds a one-screen brief, creates the branch and picks the task type.
QuestiongrillInterviews you over a decision tree until no decision is open. It looks up repo facts itself and never edits files.
Routediagnose-bug and othersBugs get a repeatable feedback loop (a failing Pest or PHPUnit test, a tinker script, a local curl). Other types go to their own skill.
Verifyverify-ps-project, blast-radiusChecks the change in the real storefront and finds what it could break outside the diff.
Reviewtask-reviewReads the diff against the task brief and the repo's AGENTS.md, on two separate axes. Read-only.
Shipmr-flowBranch, commit, push, open and merge the request, only the steps you ask for.
Close/task doneLogs the time with the numbers you give it.
LearnreflectTurns repeated corrections into skill edits you approve.

Rules

  • One owner per step. A skill that needs another loads it by name instead of copying its text.
  • Every external action waits for you: commit, push, merge request, time logging, client messages.
  • A skill that fits the chain gets a Next: line. Tools outside the chain (ps-* helpers, bootstrap skills) are not part of it.

The source of this map is docs/workflow.md in the mallard repo.

On this page