Skip to content

3.6.0

Choose a tag to compare

@andresfrei andresfrei released this 20 Nov 13:08
· 31 commits to main since this release
6de8566

Dedicated agents for repeated tasks

At the close of each work, Playbook now records the tasks the agent carried out, and proposes a dedicated agent, on a model that fits the task, for a task that repeats (work task-agents, #44).

  • Tasks recorded. At the close, prepare-project reads the git log since the previous work's close, so it also sees the previous release. It records each task it would carry out again, such as release or close-stage, in docs/wiki/tasks.md with tasks.sh, a new script of playbook-agents.

  • A proposal at 3 works. When a task is held in 3 distinct works, the agent judges its weight:

    • mechanical steps go to haiku with effort low;
    • writing text or judging a small change goes to sonnet with effort medium;
    • deciding, designing, a push, a merge, or a release stays in the main session.

    It proposes one agent at a time and always asks you.

  • Your answer. On a yes, it writes .claude/agents/<task>.md in the project, with only the steps it may run and a line naming those left to you. On a no, the task is marked declined and is not proposed again.

  • Six general rules learned from repeated review findings now ship in evidence-rules.md: three new, and three raised to level 3.

Nothing to migrate: the wiki format stays 5. The step runs only when playbook-agents is installed; docs/wiki/tasks.md is created on the first close.