Custom Prompts

If the task isn't a GitHub issue or PR, just pass a prompt. Custom prompts are implementation work — same work type as issues, just with no source fetching. The prompt is the entire brief.

wtmag create --prompt "Refactor the auth middleware to reduce duplication."

WTmag writes it to .wtmag/prompt.md, makes a worktree, and starts the agent. The worker does whatever you told it.

When to use this

• Refactors
• Research or exploration
• Writing docs
• Cleanup work
• Anything you want done in an isolated worktree but haven't filed an issue for

Be specific

A vague prompt gets vague work. Include the goal, constraints, and what you want back:

wtmag create --prompt "Audit the docs app for placeholder text. Replace it with real WTmag content. Don't touch app code."

Unlike issue workers, there's no built-in delivery workflow — the prompt is the entire brief. If you want a PR at the end, say so in the prompt. The agent won't guess.

Adding instructions to a sourced task

You can also use --prompt alongside a source like --github to add extra instructions on top of the issue context:

wtmag create --github 456 -t issue --prompt "Start by writing tests"

WTmag keeps the source context and adds your instructions. A word of caution: adding --prompt to a sourced task replaces the built-in delivery instructions (implement, commit, push, PR). Agents usually drop steps if you don't include them. Only add --prompt when you want something specific on top — and include the full workflow in your text if you still want a PR at the end.

Placement

Defaults to the implementation launch setting. Force a session if you want one:

wtmag create --prompt "Investigate flaky auth tests" -s

Window placement requires tmux.