DocsHow to create user stories in Worklayer

How to create user stories in Worklayer

Use Case: When you need to break down a feature into user stories with acceptance criteria for sprint planning Time to Complete: 5-10 minutes Prerequisites: Workspace set up, personas documented in Context/Product/, user story template available in Templates/Work/

Quick Answer

In Worklayer, you can create user stories with acceptance criteria in 5-10 minutes by referencing your personas file and using the user story template. The AI generates properly formatted stories that you can review and optionally push to Jira/Linear via MCP integration.

Step-by-Step Instructions

Step 1: Attach Personas and Feature Context

In the AI chat, use @ to reference your personas file so the stories are grounded in actual user needs.

Example:

Use @Context/Product/personas-and-use-cases.md to create user stories for [feature name].

Step 2: Reference the User Story Template

Add the user story template to ensure consistent formatting with acceptance criteria.

Example:

Use @Templates/Work/user-story-template.md to structure the stories.

Step 3: Specify the Feature and Scope

Clearly state what feature you're breaking down and any specific requirements.

Example:

Create user stories for "Task Status Management Feature" that lets users update task status from Todo → Doing → Blocked → Done.

Step 4: Generate and Review

Send the prompt and review the AI-generated stories. Check that each story follows the "As a [persona], I want [action], so that [benefit]" format.

Example full prompt:

Use @Context/Product/personas-and-use-cases.md and @Templates/Work/user-story-template.md to create user stories for "Task Status Management Feature" that lets users update task status from Todo → Doing → Blocked → Done. Include acceptance criteria in Given-When-Then format for each story.

Step 5: Save to Outcomes

After reviewing, save the user stories to the correct location for sprint planning.

Example output location:

/Outcomes/UserStories/task-status-management-stories.md

Example: End-to-End Workflow

Let's create user stories for "Task Status Management Feature."

Context:

  • Personas: Overwhelmed PM, AI-Curious PO (from Context/Product/personas-and-use-cases.md)
  • Feature: Allow users to change task status via drag-and-drop or status dropdown
  • Scope: 4 statuses (Todo, Doing, Blocked, Done), visual feedback, sync across planner surfaces

Prompt:

Use @Context/Product/personas-and-use-cases.md and @Templates/Work/user-story-template.md to create user stories for "Task Status Management Feature." Requirements: - Users can change task status via drag-and-drop between columns - Users can change task status via dropdown menu - Status changes sync across planner panel and full planner window - Visual feedback when status changes Include acceptance criteria in Given-When-Then format for each story.

Result:

AI generates user stories with:

Story 1: "Change task status via drag-and-drop"

  • As a Overwhelmed PM, I want to drag tasks between status columns, so that I can quickly update task status without opening menus
  • Acceptance Criteria:
    • Given I have a task in Todo column, when I drag it to Doing column, then the task status updates to "doing"
    • Given I drag a task, when I hover over a valid drop zone, then I see visual feedback (highlight column)
    • Given I complete the drag, when the status changes, then the task remains visible in the new column

Story 2: "Change task status via dropdown"

  • As an AI-Curious PO, I want to change task status using a dropdown menu, so that I can update status when drag-and-drop isn't convenient
  • Acceptance Criteria:
    • Given I click on a task, when I open the status dropdown, then I see all 4 status options (Todo, Doing, Blocked, Done)
    • Given I select a new status, when I confirm, then the task moves to the correct column
    • Given the status changes, when I view the planner, then the change is reflected immediately

Story 3: "Sync task status across planner surfaces"

  • As an Overwhelmed PM, I want status changes to sync across planner panel and full planner window, so that I see consistent status regardless of which view I'm using
  • Acceptance Criteria:
    • Given I change status in planner panel, when I open full planner window, then I see the updated status
    • Given I change status in full planner window, when I view planner panel, then I see the updated status
    • Given a task status changes, when I refresh the workspace, then the status persists correctly

Save to /Outcomes/UserStories/task-status-management-stories.md

Time saved: 1-2 hours of manual story writing → 10 minutes with Worklayer

Tips & Best Practices

  • Store personas once: Save personas to Context/Product/personas-and-use-cases.md so every user story references real target users instead of generic "As a user" statements.

  • Use Given-When-Then format: Structure acceptance criteria as "Given [context], When [action], Then [expected result]" for clarity and testability.

  • Keep stories small: Each story should represent 1-3 days of dev work. If a story feels too big, split it into smaller stories.

  • Reference feature context: If you have a PRD for the feature, attach it to the prompt (@Outcomes/PRDs/[feature-name]-prd.md) for more accurate stories.

  • Review for completeness: Check that acceptance criteria cover happy path, edge cases, and error states before saving.

Common Mistakes to Avoid

  • Using generic personas: If you skip @Context/Product/personas-and-use-cases.md, the AI generates generic "As a user, I want..." stories. Always attach personas for specific, user-focused stories.

  • Missing acceptance criteria: User stories without testable acceptance criteria lead to unclear requirements. Always include Given-When-Then criteria for each story.

  • Stories too large: If a story covers multiple features or takes more than 3 days to build, split it into smaller stories. Each story should be independently shippable.

Related Articles