Skip to content

Story 1.1: Create a task (full-stack) #12

Description

@github-actions

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

  1. The web app shows a "New task" form with a title field and assignee picker.
  2. Submitting the form calls the createTask GraphQL mutation.
  3. createTask validates input with zod and persists the task.
  4. The new task appears in the open list without a page reload.

Affected Repos

  • web
  • api

Tasks / Subtasks

  • (AC: 3) Add createTask mutation + zod schema in api.
  • (AC: 1, 2) Build the New task form in web and wire the mutation.
  • (AC: 4) Optimistically insert the created task into the open list.

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bmad-deliverystoryBMAD story synced from sprint-status

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions