planning-board
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when inspecting, summarizing, creating, triaging, or updating work on the Hussh Engineering Core (Project 73) or Hussh Action Items (Project 79) GitHub boards.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 4 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Avoid overlap with repo-operations and repo-context.
- Very specific: line 54
Verify the active writer identity before mutation.
- Very specific: line 56
When creating new work, create the issue before its board item.
- Very specific: line 59
When reporting work back to the user, always use the stable task shape #<number> <title>.
- Distinctive: line 60
When the user asks for labels, treat labels as a first-class part of the task update instead of leaving them implicit.
- Distinctive: line 61
Do not move sprint or reset dates on existing tasks unless the user explicitly asks for that metadata change.
- Distinctive: line 62
Do not use bare issue numbers in summaries, status lists, overdue lists, or change logs when the title is available.
- Very specific: line 63
When implementation is complete but acceptance remains, use the selected board's review state: In review on Project 73 or Ready for QA on …
- Very specific: line 64
Use Done only when the work is accepted and the issue state or acceptance evidence agrees with completion.
- Very specific: line 65
Before and after broad cleanups, run board_ops.py audit-state and resolve drift deliberately.
- Very specific: line 70
If the task is broad repo orientation, start with repo-context.
- Very specific: line 71
If the task is CI, deploy, or branch protection, use repo-operations.
- Distinctive: line 72
If the task becomes product coding or docs governance, route to the correct owner skill for that domain.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Planning Board Skill
Purpose and Trigger
- Primary scope:
planning-board-intake - Trigger on
Hussh Engineering CoreorHussh Action Itemsboard summaries, issue-backed board item creation, triage, and field updates. - Board selection:
board_ops.py --board engineering-core(default, Project 73) or--board action-items(Project 79, theInbox → Accepted → In Progress → Ready for QA → Donelifecycle). Resolve statuses and fields against the live catalog; see the per-board references. - Avoid overlap with
repo-operationsandrepo-context.
Coverage and Ownership
- Role:
owner - Owner family:
planning-board
Owned repo surfaces:
.agents/skills/planning-board
Non-owned surfaces:
repo-operationsrepo-context
Do Use
- Summarizing board activity by date window or repository slice.
- Creating issue-backed board work in
hushh-labs/hushh-research. - Updating required board metadata and verifying the resulting project-item state.
- Normalizing or updating issue labels when the user asks for label hygiene.
- Writing implementation-task handoffs for human owners and coding agents.
Do Not Use
- CI, deploy, branch-protection, or PR-approval workflows.
- Broad repo-orientation work.
- Product implementation or docs-home governance.
Read First
.agents/skills/planning-board/references/engineering-core-board.md.agents/skills/planning-board/references/action-items-board.mddocs/development/repository-map.mddocs/operations/coding-agent-mcp.md.agents/skills/planning-board/references/task-handoff.md
Workflow
- Resolve live issue/project state and existing work before creating another task.
- Verify the active writer identity before mutation; honor the user's CLI/connector preference. A CLI requirement means using the authenticated
ghidentity, not connector credentials. - For implementation tasks, follow
references/task-handoff.md: link verified owner/lead profiles; require a reasoned human brief with the owner's review reminder and actual review status; useFor coding agentsfor implementation mechanics and acceptance evidence. - When creating new work, create the issue before its board item; otherwise edit the canonical issue in place.
For Action Items, intake starts in
Inbox; use the selected board reference for acceptance, ownership, and scheduling rules. - Re-read the issue and board state after editing; verify people/reference links, preserved decisions and actual field values rather than trusting cached output.
- When reporting work back to the user, always use the stable task shape
#<number> <title>. - When the user asks for labels, treat labels as a first-class part of the task update instead of leaving them implicit.
- Do not move sprint or reset dates on existing tasks unless the user explicitly asks for that metadata change.
- Do not use bare issue numbers in summaries, status lists, overdue lists, or change logs when the title is available.
- When implementation is complete but acceptance remains, use the selected board's review state:
In reviewon Project 73 orReady for QAon Project 79. Keep unfinished implementation active; never invent a status option or infer deployment acceptance from source completion. - Use
Doneonly when the work is accepted and the issue state or acceptance evidence agrees with completion. - Before and after broad cleanups, run
board_ops.py audit-stateand resolve drift deliberately. - For duplicate board tasks, preserve scope and traceability in the canonical issue before removing the duplicate project item with
board_ops.py remove-task. Use the description when comments are disallowed; do not mark duplicates asDone.
Handoff Rules
- If the task is broad repo orientation, start with
repo-context. - If the task is CI, deploy, or branch protection, use
repo-operations. - If the task becomes product coding or docs governance, route to the correct owner skill for that domain.
Required Checks
python3 -m py_compile .agents/skills/planning-board/scripts/board_ops.py
python3 .agents/skills/planning-board/scripts/board_ops.py summary --from 2026-04-01 --to 2026-04-07
python3 .agents/skills/planning-board/scripts/board_ops.py audit-stateDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

