Agent Workflow Edit

---
name: agent-workflow-edit
description: Edit the "Workflow" section of the project instruction file — the steps to run before starting work and before delivery, in what order, and when to skip them. Use when adjusting the start-of-work / delivery flow, adding a check step, changing the workflow, or updating the workflow; also edit it per this skill when a dedicated skill affecting the before-starting-work / before-delivery flow (docs, testing, checking) has been installed or removed, when a before-starting-work or before-delivery step needs registering in the instruction file, or when the user says "from now on, before every delivery ..." or "before starting work, first ...".
---

# Editing the workflow

The "Workflow" section between `<!-- setup-agent:workflow:begin -->` and `<!-- setup-agent:workflow:end -->` in the
project instruction file is the only place in the project where the workflow is written.

When unsure, report back: stop, spell out what needs deciding (with the options) or what information is missing,
together with what you have already found out, and let the recipient of the report (the user, or the dispatcher
passing it on to the user) decide before going on; do not decide for yourself.

- Edit only between this pair of markers; the markers themselves are neither deleted nor changed.
- When no instruction file in the project carries this pair of markers, do not create it yourself: report back and
  ask the user to run the `bjj-setup-agent:workflow` installer to generate this section first, then edit it.
- When several instruction files in the project carry this pair of markers (such as `CLAUDE.md` and `AGENTS.md`),
  edit all of them together and keep them consistent; two that are symlinks of each other are the same file — edit
  only the file the symlink points to. When only some of the instruction files carry the markers, edit those and
  report which ones do not; when it is unclear which one takes effect, or the existing copies already disagree,
  report back.
- When unsure whether a step belongs in the workflow at all, or at which step, report back.

## What to write

- Each step records only dispatch: when it is done, which skill it is handed to or what command is run, which step
  it comes after, and under what circumstances it is skipped.
- Details of how belong to the skill responsible for them; to change the how, change that skill.
- Behavioral conventions about what to abide by while working (output style, subagent dispatch rules, and so on) do
  not belong in this section, are not moved in here, and are not touched here.
- Entries in "This project" must not weaken the general rules at the start of "Before delivery" (such as waiving the
  self-check or skipping user confirmation).

## Where to edit

- Everything outside the "This project" subsection is generated by the `bjj-setup-agent:workflow` installer from the
  `agent-docs`, `agent-unit-test`, `agent-gallery`, and `agent-change-check` installed in the project, and is
  rewritten wholesale on reinstall. Project-specific steps, ordering, and skip conditions are written only into the
  "This project" subsection.
- Anchor each entry on the step names, not on step numbers (numbers shift with the skills installed), e.g.
  "After 'Change check': ..." or "Skip condition for 'Add unit tests': ..." or "Move 'Documentation update' before
  'Change check'". When the step or subsection an anchor sits on is not currently there, report back.
- When writing the first entry, replace the parenthesized placeholder line in the subsection; when every entry is
  deleted, write this placeholder line back:

  ```
  (None yet. Project-specific steps are written here one per entry, anchored on the step names above, e.g. "Before 'Formatting and checks': ..." or "Skip condition for 'Formatting and checks': ..."; the full set of checks and each package's own check commands may also be written here.)
  ```
- When another skill or installer needs to register a step, it must also go through this skill to edit the "This
  project" subsection — it must not write workflow content into the instruction file itself.

## After a skill is added or removed

- What was added or removed is one of `agent-docs`, `agent-unit-test`, `agent-gallery`, `agent-change-check`: report
  back and ask the user to re-run the `bjj-setup-agent:workflow` installer to rebuild everything outside "This project";
  afterwards, list for the user, one by one, the "This project" entries anchored on steps that are now gone, and let
  the user decide whether to re-anchor or delete them.
- What was added or removed is another dedicated skill affecting the before-starting-work / before-delivery flow: add
  an entry in "This project" naming that skill, stating whether it belongs before starting work or before delivery,
  which step it comes after, and when it is skipped; for a removal, delete the corresponding entry and fix every
  other entry that mentions it. Write only the skills currently installed; leave no placeholder for ones that are
  not.

## When done

Tell the user which entries were changed, and remind them that the instruction file's changes must be committed to
version control to take effect in the project, and take effect in the next session.