micropython-stubs: Skill for Codex

Beads

Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work.

First Step

Run:

bd prime

If that prints nothing, check whether the repository has an active Beads workspace:

bd where

Preferred Route

Use the bd CLI when shell access is available. It is the most compact and direct Beads interface.

Repository Sync Policy

This repository authorizes agents to synchronize Beads-only Dolt history. It does not authorize source Git commits, pulls, or pushes.

1. Run bd dolt pull before relying on issue status or mutating Beads.
2. Search for an existing issue before creating a replacement. Continue the original issue where possible; use bd supersede <old> --with <new> for a duplicate that already exists.
3. After any successful Beads mutation, run bd dolt push before handoff.
4. Never force a Dolt push. Stop and report any pull, merge, or push conflict.

Git branch merges and rebases do not synchronize Beads. Cross-machine Beads state is carried by the Dolt remote under refs/dolt/data.

Core CLI Workflow

1. Find work:

bd ready
bd list --status=open
bd list --status=in_progress

1. Inspect before editing:

bd show <id>

1. Claim work atomically:

bd update <id> --claim

1. Create durable follow-up work when implementation reveals new tasks:

bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2

1. Close completed work:

bd close <id> --reason="Completed"

What Belongs In Beads

Use Beads for:

• shared project tasks
• blockers and dependencies
• discovered follow-up work
• work that must survive thread reset, compaction, or handoff
• status that another person or agent should be able to resume

Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state.