メニュー
Use when creating, updating, prioritizing, or querying GitHub Project todo items for omni-stream-ai/omni-code, especially backlog drafts, issue promotion, status changes, labels, and priority edits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when designing UI with OpenPencil — creating layouts via op CLI, batch design DSL, or MCP tools. Covers PenNode schema, semantic roles, typography, color, spacing, and common component patterns.
Work with Figma .fig design files and the running OpenPencil editor — inspect structure, query nodes, analyze design tokens, export images/SVG/JSX, and modify designs programmatically. Use when asked to open, inspect, export, analyze, or edit .fig files, or to control the running OpenPencil app.
Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
Entrypoint structure, exit codes, cross-platform scripts. Use when building command line utilities, scripts, or applications.
Collect coverage using the coverage packge and create an LCOV report
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
| name | omni-code-todo-management |
| description | Use when creating, updating, prioritizing, or querying GitHub Project todo items for omni-stream-ai/omni-code, especially backlog drafts, issue promotion, status changes, labels, and priority edits. |
Use this skill to keep the omni-code GitHub Project organized and consistent. Backlog stays draft-only; Todo and later use real GitHub issues.
https://github.com/orgs/omni-stream-ai/projects/2Backlog for draft items only.Todo.Todo.In Progress.In Progress should usually have one owner.Backlog: draft only, not yet an issue.Todo: real issue exists, but no branch yet.In Progress: actively being worked on and should usually have a linked branch.Review: waiting for review or verification.Blocked: waiting on a dependency.Done: complete and verified.Use these base labels:
bugfeaturerefactordocstestinfraHigh: core session, agent, or model behavior.Medium: session settings, model controls, or tool output UX.Low: polish, navigation, or convenience work.gh project item-list 2 --owner omni-stream-ai --format json.gh project item-create 2 --owner omni-stream-ai --title ... --body ....omni-stream-ai/omni-code, add labels, and move Status to Todo.In Progress, create a linked branch from the issue's Development relationship, and fetch that branch into the local repository.gh project item-edit to change title, body, status, and priority.gh project field-list 2 --owner omni-stream-ai --format json before editing if needed.Use the bundled scripts for the recurring operations:
scripts/create_backlog_draft.sh "<title>" "<body>" [priority]scripts/promote_draft_to_todo.sh <project-item-id-or-exact-title> [labels]scripts/start_issue_work.sh <issue-number> [branch-name] [--checkout]scripts/list_project_items.sh [status]The scripts intentionally follow the current workflow:
--checkout additionally switches the local worktree to that branchDI_.PVTI_.references/project-facts.md for current field and option IDs.feat/2-continuous-voice-conversations.