derive_features
Generate a proposed feature checklist from documentation and existing features, then add it to the backlog for approval, skipping any candidates that already exist.
Instructions
Derive a feature checklist for a goal from the documentation and existing features, and put it straight in the backlog at 'proposed' — recorded, not yet agreed. Defining a goal must produce work, not just an objective. Call project_boundaries FIRST: re-proposing something already refused wastes a review round and teaches the principal that the queue does not learn. Candidates matching an existing feature are reported rather than created.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"goal": "<goal>",
"candidates": "<candidates>"
},
"name": "derive_features"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Directory identifying the project and the tree. Defaults to this session's working directory, which in a git worktree is that worktree. | |
| goal | Yes | ||
| note | No | ||
| actor | No | ||
| source | No | What was read to derive these. | |
| candidates | Yes |