DocsHow to use templates in Worklayer

How to use templates in Worklayer

Use Case: When you want consistent formatting for deliverables like PRDs, user stories, and stakeholder updates Time to Complete: 5 minutes Prerequisites: Workspace set up with Templates/ folder created


Quick Answer

In Worklayer, templates are markdown files stored in Templates/ that define the structure for common deliverables. Reference templates using @ in your prompts, and AI generates outputs following your standard format every time.


Step-by-Step Instructions

Step 1: Create Templates Folder

Set up a Templates/Work/ folder in your workspace to store reusable templates.

Example structure:

Templates/ └── Work/ ├── prd-template.md ├── user-story-template.md ├── stakeholder-update-template.md └── meeting-notes-template.md

Step 2: Create or Customize Templates

Either use Worklayer's starter templates or create your own.

Example: prd-template.md

# PRD: [Feature Name] ## Executive Summary [1-2 paragraph overview] ## Problem Statement [What problem are we solving and for whom?] ## Success Metrics | Metric | Baseline | Target | Owner | |---|---|---|---| ## User Stories [List of user stories with acceptance criteria] ## Rollout Plan - Phase 1: Alpha (timeline, scope) - Phase 2: Beta (timeline, scope) - Phase 3: GA (timeline, scope)

Step 3: Reference Templates in Prompts

Use @ to reference templates when generating outputs.

Example:

Use @Templates/Work/prd-template.md to draft a PRD for [feature name].

Step 4: Generate Output

AI follows the template structure exactly, filling in each section with content based on your context files.

Step 5: Save and Reuse

Save the generated output to Outcomes/ and reuse the template for future deliverables.


Example: End-to-End Workflow

Let's create a user story template and use it.

Step 1: Create user story template:

# User Story: [Story Name] **As a** [persona], **I want to** [action/capability], **So that** [benefit/outcome]. **Priority**: [P0 / P1 / P2] **Estimate**: [Story points or time] ## Acceptance Criteria - [ ] Given [context], when [action], then [expected result] - [ ] Given [context], when [action], then [expected result] ## Notes [Any additional context or technical considerations]

Save to Templates/Work/user-story-template.md

Step 2: Reference template in prompt:

Use @Context/Product/personas-and-use-cases.md and @Templates/Work/user-story-template.md to create user stories for "File Search Feature."

Step 3: AI generates stories:

# User Story: Search files by name **As an** Overwhelmed PM, **I want to** search files by name in the workspace, **So that** I can quickly find documents without browsing folders. **Priority**: P1 **Estimate**: 3 story points ## Acceptance Criteria - [ ] Given I type in the search box, when I enter a filename, then I see matching files - [ ] Given search results are displayed, when I click a result, then the file opens in center panel

Step 4: Save to Outcomes/UserStories/file-search-stories.md

Result: Every user story follows the same format because the template is reused.

Time to create template: 5 minutes once Time to use template: 0 minutes (just reference with @)


Tips & Best Practices

  • Start with 3-4 core templates: Create templates for your most common deliverables (PRDs, user stories, stakeholder updates). Add more templates as needed.

  • Include instructions in templates: Add comments like [1-2 paragraph overview] to guide AI on what content to generate for each section.

  • Use tables for structured data: Templates with tables (metrics, user stories, acceptance criteria) produce consistent, scannable outputs.

  • Customize starter templates: Worklayer includes example templates. Copy them to your workspace and customize sections to match your team's format.

  • Version templates: If your template format changes, save the old version (prd-template-v1.md, prd-template-v2.md) so old documents remain compatible.


Common Mistakes to Avoid

  • Creating too many templates: Don't create 15 templates on day one. Start with 3-4 templates for common deliverables and add more as you discover patterns.

  • Overly rigid templates: If your template is too prescriptive (e.g., "Exactly 5 bullet points"), AI may struggle to adapt to different contexts. Keep templates flexible.

  • Not referencing templates: If you don't use @Templates/Work/prd-template.md in your prompt, AI will generate outputs in its own format instead of following your standard.