Work Skill

Pick up a story from the active sprint and implement it end-to-end.

Notion IDs

Steps

Follow these steps in order. Stop and report if any step fails.

1. Find the active sprint

Use notion-search to find the sprint with Status = "Active". Fetch the sprint page to get its linked stories.

If no active sprint exists, tell the user and stop.

2. Select a story

From the active sprint's stories, fetch each story to check its status. Pick a story using this priority order:

1. •In Progress — resume work already started (highest priority)
2. •TODO — start new work

Skip stories with status Done, In Review, or In Test.

If multiple candidates exist at the same priority level, prefer higher priority stories (Critical > High > Medium > Low).

If $ARGUMENTS is provided, use it to match a specific story by name or keyword instead of auto-selecting.

If no actionable stories remain, tell the user the sprint is complete and stop.

3. Fetch story details and tasks

Fetch the selected story page to get:

• •The story description (page content) for context
• •The linked tasks

Fetch each task to get its title, status, type, notes, and estimate.

4. Update statuses to In Progress

Update ALL statuses immediately when starting work — including during planning, not just coding.

1. •Move every task in the story from TODO → In Progress using notion-update-page
2. •Move the story from TODO → In Progress
3. •If the parent epic is in TODO or Not Started, move it to In Progress
4. •If the parent milestone is in TODO or Not Started, move it to In Progress

Do not skip updating tasks. All tasks must be marked In Progress before proceeding to the next step.

5. Present the work summary

Show the user:

• •Sprint name
• •Story title and description
• •List of tasks with their status, type, and estimate
• •Which tasks are already done vs remaining

6. Plan implementation

Enter plan mode. For each remaining task (not Done), analyze what code changes are needed by exploring the codebase. Write a concrete implementation plan that covers all remaining tasks.

Present the plan to the user for approval via ExitPlanMode.

7. Implement tasks

After the plan is approved, work through each remaining task in order. For each task:

1. •Update the task status to In Progress in Notion using notion-update-page
2. •Implement the changes described in the plan
3. •Run pnpm check and pnpm test to verify the changes compile and pass tests

Leave tasks in In Progress after implementation — the commit step handles pushing and moving them to Done.

If a task fails (tests break, types don't pass), fix the issue before moving on. If you cannot fix it, leave the task as In Progress and report the blocker to the user.

8. Create a feature branch

Before writing any code, ensure you're starting from a clean, up-to-date main:

git checkout main
git pull origin main
git checkout -b feat/story-name

This must happen before step 7 (implementing tasks).

Branch rules:

• •Always create a new branch from main for each story. Never reuse an old feature branch for a new story.
• •If you're resuming in-progress work that already has an unmerged branch for the same story, switch to that branch and rebase on main instead.
• •If a previous branch for a different story exists, ignore it — start fresh from main.

9. Commit and push to feature branch

After all tasks are complete (or as many as possible):

1. •Invoke the /commit skill to commit, push, and verify CI
2. •The commit skill will move tasks to Done only after CI checks pass, and cascade to the story if applicable

Never push directly to main. All work goes through feature branches and pull requests.