neutral/trellis

Create or revise the exact project Playbook the user requests, including when they invoke /capture-playbook. Use the request as the design brief, ask only questions that materially change the Playbook, and write the agreed Playbook in the selected Trellis root. Do not mine conversations or discover candidates; route reflective requests to /discover-playbooks. Supporting mechanics may use a private safe _cli tool or an explicitly requested project-owned script.

Examine only the current session or exact sessions the user selects to recommend reusable Playbooks. Use when the user asks to discover Playbooks or invokes /discover-playbooks. Ask only questions that materially change a recommendation and return one or more self-contained /capture-playbook prompts. Never scan ambient history, write files, or invoke Capture Playbook automatically.

Review a Trellis Playbooks collection when the user asks for an audit or invokes /trellis-audit. Inspect setup, Playbooks, supporting tools, and explicitly scoped project scripts; report evidence-backed improvements without changing, executing, pruning, or blocking owner-controlled scaffolding.

Initialize or adopt a project-local Playbooks folder for Trellis. Use when the user asks to set up Trellis, chooses a Playbooks location, or invokes /trellis-init. Default to playbooks/ but let the user select another project-local folder. Create only the marked collection README and return an optional AGENTS.md snippet; never edit AGENTS.md, install dependencies, create a launcher, or stage, commit, push, or publish changes.