Story 1.1: Create a task (full-stack)
Status: ready-for-dev
Example artifact for the meta-router example branch. The Affected Repos
section below is what the bmad-dev-story customization reads to decide how
many git worktrees to create — here, two.
Story
As a user, I want to create a task with a title and optional assignee, so that my
work is tracked from one place.
Acceptance Criteria
- The web app shows a "New task" form with a title field and assignee picker.
- Submitting the form calls the
createTask GraphQL mutation.
createTask validates input with zod and persists the task.
- The new task appears in the open list without a page reload.
Affected Repos
Tasks / Subtasks
Dev Notes
This is a full-stack story. When implemented, meta-router creates a worktree per
affected repo:
workspaces/alpha/implementation/1-1-create-a-task/web/ # branch story/1-1-create-a-task
workspaces/alpha/implementation/1-1-create-a-task/api/ # branch story/1-1-create-a-task
Implement the web and api changes in their respective worktrees and open one PR
per repo off the shared story/1-1-create-a-task branch.
Source tree components to touch
api: GraphQL resolvers, zod schemas, task model.
web: task creation form component, GraphQL client hooks, open-list view.
Story 1.1: Create a task (full-stack)
Status: ready-for-dev
Story
As a user, I want to create a task with a title and optional assignee, so that my
work is tracked from one place.
Acceptance Criteria
createTaskGraphQL mutation.createTaskvalidates input with zod and persists the task.Affected Repos
Tasks / Subtasks
createTaskmutation + zod schema inapi.weband wire the mutation.Dev Notes
This is a full-stack story. When implemented, meta-router creates a worktree per
affected repo:
Implement the web and api changes in their respective worktrees and open one PR
per repo off the shared
story/1-1-create-a-taskbranch.Source tree components to touch
api: GraphQL resolvers, zod schemas, task model.web: task creation form component, GraphQL client hooks, open-list view.