petar-djukic/coding-skills

bd-issue-pop

Pop a bead (epic) into a worktree branch, decompose it into child beads, then

gh-issue-pop

Pop a GitHub issue, decompose it into sub-issues on a worktree branch, and open

do-work

Work one unit from the epic you popped. Pick the workflow by deliverable:

make-work

Read `docs/VISION.yaml` (goals and boundaries), `docs/ARCHITECTURE.yaml`

test-clone

Test the orchestrator library by deploying it into a target Go repository and running the test plan. Failures indicate bugs in the orchestrator code,

gh-release-push

Tag and push a release from green `main`.

align-specs

Read **docs/constitutions/design.yaml** first and hold it as the authority for the rest of this session.

bootstrap

I'm starting a new project and need you to help me create the initial documentation.

exp-start

Create or join an experiment branch. Experiments run on short-lived `exp/<slug>` branches in a dedicated worktree. They never merge to `main` and neve

gh-issue-push

Create a GitHub issue in the current repository.

bd-issue-push

Create a bead (task) in the current repository using beads (`bd`). Beads keeps its database in the main repo checkout and its tracked `issues.jsonl` o

bd-issue-show

List beads or show details of a specific bead in the current repository.

exp-stop

Conclude and delete an experiment branch. Shows pending work and a diffstat for a final review, then deletes the current repository's experiment branc

gh-issue-show

List GitHub issues in the current repository, or show details of a specific issue. Use when the user wants to browse issues, look up an issue by numbe