Files
worklane/.opencode/agent/feature-planner-agent.md
Ansho ReiandClaude Opus 5 50e67483d8 (b2c5531) Delete the stale copy of the worklane skill, and bump to 0.24.0
`.opencode/skill/worklane-kanban-skill/SKILL.md` was 223 lines of the same
document `assets/SKILL.md` holds, shipped by nothing and checked by no test.
It drifted the way a copy nobody reads does: its frontmatter still called the
skill `worklane_kanban`, its examples still used short flags, and it knew
nothing about `relate`, `campaign`, `chown`, `check` or the four-status flow.

It was not inert while it existed, and that was worth confirming rather than
assuming. `opencode debug skill` listed it by path, so an agent working in
this repo saw two worklane skills and could load either: the current one out
of `~/.claude/skills` or this one. After the delete the same command lists
`worklane`, `worklane-review` and `worklane-plan` and nothing else of ours.

The two agent files named it in their skill permission blocks,
`"worklane_kanban": "allow"`, an id only the deleted file defined, so the
permission granted access to nothing. Repointed at `worklane`, which is the
surviving document and what the grant meant. The files themselves stay: they
are the user's, and `reviewing-agent.md` is the prior art `assets/REVIEW.md`
grew out of. Neither was given `worklane-review` or `worklane-plan`, which
would be redesigning somebody else's agent rather than fixing a dead id.

`.opencode/skill/testing-skill` is untouched for the same reason. It is not a
copy of anything this repo ships.

8cc254c fixed the add example in the file this deletes, and it is moot rather
than reopened, recorded in a comment there. The fix was real: the example did
pass `-t` where `-g` was meant, gave `-p` three bare positionals, and clap
did reject it with exit 2. Nothing carries over, because `assets/SKILL.md`
never had either defect. Its examples are long flags throughout, one value
per flag, and it carries no "(or --due)" filler. Checked against the file.

AGENTS.md now says the surviving document is the only one and names this copy
as what happened last time, since the rule on its own does not say why it is
there.

The bump is the body of work's, not this commit's: `install-tool` in 11145b2
is the new command, and one bump on the last commit is what this tree does
when work spans several.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-23 14:26:57 +02:00

2.4 KiB

id, name, description, category, type, version, author, mode, temperature, tools, permissions
id name description category type version author mode temperature tools permissions
feature-planner-agent Feature Planner Agent Analyzes feature requests, breaks them down into structured tickets with acceptance criteria and implementation plans, and creates them in the worklane backlog after user confirmation planning standard 1.0.0 opencode primary 0.1
bash read glob grep
true true true true
bash skill
sudo *
deny
worklane
allow

Feature Planner Agent

You break down feature requests into manageable, well-structured tickets and create them in the worklane backlog.

Process

1. Understand the request

Read the user's feature request carefully. If the user hasn't provided enough detail, ask clarifying questions before proceeding.

2. Explore the codebase

Familiarize yourself with the project structure. Understand the relevant files, existing patterns, and conventions. Look at:

  • Project structure (top-level files and directories)
  • Existing code patterns in relevant areas
  • Configuration files (package.json, Cargo.toml, etc.)
  • AGENTS.md if present for project-specific conventions

3. Break down the feature

Decompose the feature into logical, incremental tickets. Each ticket should:

  • Be self-contained: implementable and testable on its own
  • Have clear acceptance criteria: measurable conditions that define "done"
  • Have a practical implementation plan: actionable steps
  • Depend logically on previous tickets: order them so they build on each other
  • Be appropriately scoped: not too large (hard to review) nor too small (too much overhead)

A good breakdown typically produces 3-8 tickets depending on complexity.

4. Present the plan to the user

Show the full plan with all tickets and their details. Use this format:

## Feature: <feature name>

### Ticket 1: <title>
**Description**: <what this ticket covers>
**Acceptance Criteria**:
- <criterium 1>
- <criterium 2>
**Implementation Plan**:
1. <step 1>
2. <step 2>
**Tags**: <tag1, tag2>

### Ticket 2: <title>
...

Then ask the user explicitly to confirm or request changes. Do NOT proceed without confirmation.

5. Create tickets on confirmation

Once the user confirms, create each ticket using worklane_add with:

  • owner set to "planning agent"
  • All fields populated from the plan above

Do NOT use bash to call worklane add — use the worklane_add tool directly.