Features and tasks

Bedrock tracks the work itself on two kanban boards: Features for the capabilities you’re building, and Tasks for the actionable steps that get them done. Both live on the left rail and are scoped to the active product.

Features

A feature is a unit of product work — a capability you’re shipping. The features board has four columns:

idea → planned → in-progress → shipped

Drag a card between columns to change its stage.

Creating a feature

Quick capture: click + at the top of the Idea column, type a title, press Enter.

Full detail: click New feature in the board header to set stage, priority, and release link up front.

Feature fields

Field	Description
Title	Short name for the feature
Stage	Current kanban column
Priority	High (red dot) · Med (amber dot) · Low (gray dot)
Release	Optional link to a release
Description	Markdown field for acceptance criteria and context

Feature progress

Each feature card shows a task progress count (e.g. “3/5 tasks done”). The progress is calculated from the feature’s linked tasks — when all tasks reach Done, the feature is ready to be moved to Shipped.

Tasks

A task is a concrete piece of work. The tasks board has three columns:

to-do → in-progress → done

Drag a card between columns to change its status.

Creating a task

Quick capture: click + at the top of the To Do column, type a title, press Enter.

Full detail: click New task in the board header.

Task fields

Field	Description
Title	Short action-oriented name
Status	To Do / In Progress / Done
Priority	High · Med · Low
Due date	Optional — drives the Today view buckets
Notes	Long markdown field for context and instructions
Feature	Optional parent feature link
Release	Optional release link (when no feature is set)
Checklist	Sub-steps to tick off within the task
Doc refs	Workspace docs relevant to this task
Attachments	Files copied into `.bedrock/attachments/`

Task checklists

Break a task into sub-steps with a checklist:

Click Add item to append a checklist entry.
Tick boxes to mark sub-steps done.
Drag items to reorder.

Example checklist for “Implement JWT refresh”:

[ ] Design the token schema
[ ] Write the refresh endpoint
[ ] Add unit tests
[ ] Update OpenAPI spec

Due dates

Set a due date and the task appears in the Today view under the appropriate bucket:

Overdue — past the due date (red)
Due today — due today (amber)
This week — due within 7 days

The dashboard also shows overdue and due-today counts as alert tiles.

How they fit together

Features describe what you’re building and hang off releases; tasks describe how and hang off features. Together they give a top-down view:

release → feature → task → checklist item

You can edit task progress inline from the release detail view, so the release page doubles as a planning board for that milestone.