メニュー
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Maintain AI proposal discovery and form preparation when adding or updating Agreements create routes. Use when adding a new proposal type, changing create form fields, or updating select-create-action / select-settings-action menus.
Scaffold an SDD ticket workspace when starting a new unit of work. Reads the developer config, classifies the task, picks the SDD level, and creates the ticket folder in hypha-context. Trigger when the developer says: 'I'm starting #X', 'let's begin <ticket>', 'new task', or 'starting work on X'. (To resume an in-progress ticket use hypha-task-resume. To wrap up use hypha-checkpoint.)
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.
Surface an idea, observation, or proposal for team discussion without owning the improvement — creates a committed entry in the shared feedback/ folder in hypha-context. Two flavors: internal (engaged dev flagging something to discuss collectively) or external (any contributor providing input for engaged devs to act on). Trigger when someone says: 'flag this for the team', 'I have feedback on X', 'log this idea without a ticket', 'note this for discussion', 'I want to surface this but not own it'.
Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.
| name | hypha-board |
| description | Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move |
| audience | dev |
Triggers: "update the board", "sync this to GitHub", "move #X to In Review", "open the PR", "what's assigned to me", "check GitHub", creating/closing a ticket.
Who it's for: Technical developers with github.enabled: true in their general AGENTS.local.md.
Skip silently for others — never offer it if the gate isn't set.
Gating (check first):
AGENTS.local.md has github.enabled: true and a technical profile.gh CLI is installed and authenticated — run gh auth status. Board commands need the project
scope: gh auth refresh -s project (offer the command; do not run silently).Golden rule: reads are free; every write states the exact change and asks for a yes first.
Full procedure in hypha-context: workflow/github-sync.md
Issue/PR conventions (title format, label taxonomy, board columns, custom fields):
planning/issue-guidelines.md
Don't duplicate those here. When in doubt, read them.
Repo: hypha-dao/hypha-web
Project board: Hypha Platform — Active Work (board #14)
Board columns: Backlog → Todo → In Progress → Blocked → In Review → Done
Issue title convention: type(scope): short description (e.g. fix(banking): tab count wrong)
Label taxonomy (active labels — from issue-guidelines.md):
| Label | Use for |
|---|---|
bug | Something broken |
banking | All Bridge/fiat banking work |
new feature | Feature or capability addition |
chore | Housekeeping, config, infra |
documentation | Docs, onboarding |
analysis | Design/research with a decision as output |
blocked | Blocked on external dependency |
Hotfix | Needs to ship urgently |
AI-Generated Feature | AI-generated issues (for transparency) |
For the complete, authoritative list see
planning/issue-guidelines.mdin hypha-context.
hypha-task-init: read the linked GitHub issue to ground the spec. If no issue exists
and the work belongs on the board, offer to create one with the correct title/labels/board
placement — then ask for a yes before creating.hypha-checkpoint: offer to reflect the session on GitHub — progress comment,
board-column move (e.g. In Progress → In Review when a PR opens), label/field updates. State the
proposed write and wait for a yes.