hirogakatageri/clear-board
plugins/guild/skills/clear-board/SKILL.md
This skill should be used when the user asks to "clear the board", "reset the guild", "start fresh", "wipe the board", "clear all tasks", "reset the board", or wants to remove all current work from the guild board and start over.
$ install --global
skillsauthnpx skillsauth add hirogakatageri/hirokata clear-boardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 8:09 AM119.6s1 file scanned
SKILL.md
- name:
- clear-board
- description:
- >
- version:
- 1.0.0
- user-invocable:
- true
Clear Board — Reset the Guild
Wipe all tasks, requirements, and plans from the guild board and reset it to a clean state.
Steps
1. Check for Guild
Read .guild/BOARD.md.
If not found:
No guild board found. Nothing to clear.
Run /guild:check-in to initialize a new guild.
Stop here.
2. Inventory the Board
Count items in each category:
- Requirements: count rows in the Requirements table in BOARD.md
- Tasks in progress: count rows in the In Progress table
- Tasks in backlog: count rows in the Backlog table
- Completed tasks: count rows in the Done table
- Plan files: count files in
.guild/plans/
3. Confirm with User
Present the current state and ask for confirmation:
Current board state:
{N} requirement(s)
{N} task(s) in progress
{N} task(s) in backlog
{N} task(s) completed
{N} plan(s)
This will permanently delete all requirements, tasks, and plans.
Are you sure you want to clear the board? (yes / no)
If the board is already empty (all counts are 0):
The guild board is already empty — nothing to clear.
Stop here.
If "no" or anything other than an explicit confirmation: Stop without making any changes.
If "yes": Proceed to step 4.
4. Clear the Board
- Delete all files in
.guild/requirements/(keep the directory) - Delete all files in
.guild/tasks/(keep the directory) - Delete all files in
.guild/plans/(keep the directory, including any slice subdirectories)
NEVER touch .guild/docs/ — the knowledge base is evergreen and survives board resets. Researcher findings accumulate across requirements and should not be lost when clearing the board.
NEVER touch .guild/archive/ — prior releases stay archived.
Use Bash to delete only the cleared directories' contents:
rm -rf .guild/requirements/* .guild/tasks/* .guild/plans/*
The -r flag removes plan slice subdirectories (e.g. .guild/plans/PLAN-001/). .guild/docs/ and .guild/archive/ are not in the glob, so they remain untouched.
5. Reset BOARD.md
Overwrite BOARD.md with a clean slate, preserving today's date as last-checkin:
---
next-task: 1
next-req: 1
next-plan: 1
last-checkin: {today's date}
---
# Guild Board
## In Progress
| Task | Title | Agent | Req | Since |
|------|-------|-------|-----|-------|
## Backlog
| Task | Title | Agent | Req | Priority | Created |
|------|-------|-------|-----|----------|---------|
## Done
| Task | Title | Agent | Req | Completed |
|------|-------|-------|-----|-----------|
## Requirements
| Req | Title | Status | Progress |
|-----|-------|--------|----------|
6. Confirm
Board cleared.
Removed: {N} requirement(s), {N} task(s), {N} plan(s)
Counters reset to: REQ-001, TASK-001, PLAN-001
Run /guild:new-requirement to add work, or /guild:check-in to start a session.
Rules
- Always confirm before deleting — this action is irreversible
- Keep directories — only delete files, not the
.guild/requirements/,.guild/tasks/,.guild/plans/folders themselves - Never clear
.guild/docs/— the knowledge base is evergreen and preserved across resets - Never clear
.guild/archive/— prior releases stay archived - Reset all counters to 1 — prevent ID confusion on the fresh board
- Update last-checkin — so the board reflects when it was last touched
Related Skills
hirogakatageri/verify-and-fix
development
VerifiedTrustedCommunity
This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found a bug", "got an error", "debug this", "this is broken", "fix this error", "verify and fix", or any message that includes a stack trace or error output. Runs a structured workflow: gather context, investigate configured log/code sources, report root cause with ranked solutions, then apply a test-driven fix.
5SKILL.mdUpdated Jun 5, 2026
hirogakatageri/svelte-env-vars-check
testing
VerifiedTrustedCommunity
This skill should be used when the user says "check svelte env vars", "check environment variables", "validate env vars", "check env var patterns", "audit environment variables", "audit env vars", "check SvelteKit env", "svelte env check", or any phrase asking to audit or validate SvelteKit environment variable usage patterns.
5SKILL.mdUpdated May 25, 2026
hirogakatageri/save-log
data-ai
VerifiedTrustedCommunity
Internal skill used by the session-tracker logger agent to append a session entry to .logs/YYYY-MM-DD-log.md, creating the file and directory if needed. Not user-invocable.
5SKILL.mdUpdated May 20, 2026
hirogakatageri/query-changes
data-ai
VerifiedTrustedCommunity
Internal skill used by the session-tracker logger agent to query git for committed and uncommitted changes in the past 28 hours. Not user-invocable.
5SKILL.mdUpdated May 20, 2026