Skip to content

po4yka/RIPDPI / .agents/skills/repo-task-board

repo-task-board

Verified

Router for the ./taskctl portfolio-task lifecycle. Use when creating, updating, triaging, executing, reviewing, or closing RIPDPI tasks, backlog items, bugs, epics, or OpenSpec-backed work.

Repository task board

docs/tasks/issues/*.md is the portfolio source of truth. docs/tasks/board.md is generated. Execution lives in exactly one of:

  • simple work: docs/tasks/work/<TASK-ID>.md;
  • specification-driven work: openspec/changes/<change>/tasks.md.

Use only ./taskctl for lifecycle operations:

  • inspect: list, show, ready, graph;
  • create/start/update: new, start, transition, steps;
  • validate: verify, validate, generate-board;
  • complete: openspec archive, then close prepare --outcome done, commit, and later close purge in a separate commit;
  • drop: close prepare --outcome dropped, commit its receipts, then openspec archive and close purge before the deletion commit.

Stable IDs are area-prefixed with globally unique 16-digit numeric suffixes. Worktrees share a locked allocator reservation through the Git common directory; committed validation catches cross-clone collisions. blocked_by is canonical; reverse blocks is derived. See docs/tasks/README.md's "OpenSpec decision" section for the exact spec_mode: required criteria -- do not re-derive or paraphrase that list here. Never hand-edit the generated board, use direct upstream archive, pass --no-validate, close work without evidence, or delete a record before its terminal-state commit exists.

Before parallel agents write, record ownership and serialized shared-file lanes in the portfolio task. All implementation work uses a dedicated worktree and follows AGENTS.md.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall