💡 Workflow Template Gallery: Curated Starting Points for Non-Technical Users

[github-actions[bot]]

Summary

Provide a browsable gallery of pre-built, curated workflow templates (brainstorming, competitive analysis, sprint planning, meeting prep, report generation) that non-technical users can launch with one click. The avatar presents templates conversationally based on user role and past usage, solving the cold-start "what can I do?" problem that blocks non-technical adoption.

Market Signal

Every successful AI product provides structured starting points: ChatGPT has custom GPTs, Codex has Skills, Zapier has 6,000+ templates, and workflow automation tools universally offer template galleries. The 2026 trend toward low-code/no-code accessibility (Airtable, Codewords, Composio) confirms that non-technical users need guided entry points, not blank canvases. CodeWords' chat-native approach where users describe needs in plain English aligns with TalkTerm's conversational model.

User Signal

TalkTerm's PRD targets non-technical knowledge workers (Journey 1: Sarah the PM). The current design assumes users know what to ask for. But non-technical users' biggest barrier is not knowing what's possible. BMAD workflows (brainstorming, PRD creation, architecture review) are the project's primary use case and natural first templates. Zero feature requests exist because the product hasn't shipped, making pre-launch UX decisions critical.

Technical Opportunity

Templates are structured prompt flows + MCP server configurations — lightweight metadata, not heavy infrastructure. The existing BMAD method repository (silently cloned as default workspace per FR52-FR53) already contains workflow definitions. Templates map to the ActionCard system (UX-DR2): avatar presents template options as left-panel cards, user selects, avatar initiates the workflow. No new architectural components needed — templates are a content layer over existing systems.

Assessment

Dimension	Score	Rationale
Feasibility	high	Templates are metadata + prompts over existing ActionCard and agent pipeline infrastructure; no new systems needed
Impact	high	Solves the critical cold-start problem for non-technical users; every successful AI product has templates
Urgency	med	Critical for launch success but not time-sensitive to a specific external event; should be designed alongside Epic 2-3

Adversarial Review

Strongest objection: Templates might make TalkTerm feel rigid or limited, reducing it to a menu-driven tool rather than a flexible AI assistant.

Rebuttal: Templates are starting points, not constraints. The avatar presents them as suggestions: "These are popular starting points — or just tell me what you need." Templates expand perceived capability by showing what TalkTerm CAN do, while the open-ended conversation always remains available. Data from Zapier and ChatGPT GPTs shows that template-driven discovery significantly increases user activation and retention. The avatar's conversational presentation prevents the "rigid menu" feeling.

Suggested Next Step

Define the initial template schema (name, description, category, required MCP servers, prompt flow steps) and curate 5-8 BMAD workflow templates as the launch set. Add a template selection flow to the avatar greeting sequence (FR33).