arthai-marketplace

/templates

Generate structured deliverables from templates.

Synopsis

/templates [type] [topic]

When to use it

You need a professional non-engineering deliverable fast: a product brief, launch plan, status report, design critique, meeting briefing, blog post, or user persona
You’re a PM, marketer, or stakeholder who wants outcome-focused documents grounded in real project data
Not for: full feature PRDs with engineering feasibility — that’s /planning; or formatting an existing document for distribution — that’s /share
Prerequisite: status-report reads your git history, PRs, and issues — a sparse repo with little activity will produce a thin report; the other templates just need a topic

Quickstart

/templates product-brief notifications

What you’ll see: a specialist is brought in and a plain-language product brief (problem, target user, desired outcome, success metrics, scope, open questions) is generated for “notifications”, under 500 words, followed by next-step options.

Examples

/templates                                  # show the selection menu
/templates product-brief notifications     # product brief for a feature
/templates launch-plan dark-mode            # go-to-market launch plan
/templates status-report                    # stakeholder status report from git/PR/issue data — no topic argument needed
/templates design-critique login-page       # design evaluation against proven principles
/templates meeting-briefing sprint-planning # pre-meeting briefing with project context
/templates blog-post launch-announcement    # blog post grounded in real product capabilities
/templates user-persona pm-users            # behavior-based personas; pass a file path, pasted notes, or a segment name as the topic

Arguments & flags

Argument	Values	Default	What it does
`[type]`	`product-brief`, `launch-plan`, `status-report`, `design-critique`, `meeting-briefing`, `blog-post`, `user-persona`	none; shows a selection menu if omitted	Which deliverable to generate
`[topic]`	free text	none; asked if needed	What the deliverable is about; `status-report` needs none

What it does

Selects the template — if no type is given, presents a numbered menu of the seven templates (user-confirmation checkpoint). If the type needs a topic and none was provided, it asks for one (user-confirmation checkpoint); with a topic inline it goes straight to generation.
Brings in the right specialist — each template routes to a dedicated agent with a structured prompt that reads your project context (CLAUDE.md, git history, PRs, issues as relevant). Output is plain language, jargon-free, and length-bounded per template.
Offers next steps — after every output: “share this” (formats it via /share), “revise [section]”, or “try another template”.

Output & artifacts

The finished deliverable in the conversation, ready to revise or hand to /share for distribution
No files are written by default

Troubleshooting

Problem	Fix
Menu appears when you expected generation	Pass the type (and topic) inline: `/templates product-brief notifications`
Status report looks thin	It reads git history, PRs, and issues — sparse repos produce sparse reports; add a topic to focus it
Design critique asks what to critique	Provide a URL, screenshot path, or description of the design
User persona output feels generic	Point it at real research data (interview notes, support tickets, survey responses) rather than just a segment name
A specialist is unavailable	The skill explains what happened in plain English and suggests an alternative

/share — format any template output for Slack, Twitter, HTML, or markdown
/planning — full PRD with engineering feasibility, for features headed to implementation
/welcome and /wizard — non-engineer entry points that route into these templates