create-type-httlisted

<purpose> Create custom deliverable types that extend heres-the-thing beyond the builtin types. Each type defines a template, output format, required tools/MCP servers/external binaries, and instructions for the deliverable agent. Custom types are registered in `~/.things/heres-the-thing/deliverable-types/index.json` and can be included in any campaign goal's `deliverables` list. </purpose> <steps> <step id="load-config" number="1"> <description>Load Configuration</description> <load-config> Resolve the user's home directory (run `echo $HOME` via Bash). Use this absolute path for all file operations below -- never pass `~` to the Read tool. 1. Read `<home>/.things/config.json` <if condition="config-missing">Tell the user: "Run `/things:setup-things` first." Then stop.</if> 2. Read `<home>/.things/heres-the-thing/deliverable-types/index.json` <if condition="types-missing">Tell the user: "Run `/heres-the-thing:setup-htt` first." Then stop.</if> </load-config> </step> <step id="gather-type-info" number="2"> <description>Gather Type Information</description> Use AskUserQuestion to gather: 1. **Name**: What should this deliverable type be called? (e.g., "Executive One-Pager", "Stakeholder Update Email", "Decision Matrix") 2. **Description**: What does this deliverable produce? What's it for? 3. **Output format**: What format should the output be in? <options> - md (Markdown) - pdf (PDF