github-project-board-1-board-initialization
Sub-skill of github-project-board: 1. Board Initialization (+3).
Best use case
github-project-board-1-board-initialization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of github-project-board: 1. Board Initialization (+3).
Teams using github-project-board-1-board-initialization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1-board-initialization/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-project-board-1-board-initialization Compares
| Feature / Agent | github-project-board-1-board-initialization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of github-project-board: 1. Board Initialization (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 1. Board Initialization (+3)
## 1. Board Initialization
```bash
# Create a new project board
gh project create --owner @me --title "Development Board"
# Get the project number
PROJECT_NUM=$(gh project list --owner @me --format json | \
jq -r '.projects[] | select(.title == "Development Board") | .number')
# Add custom fields for swarm tracking
gh project field-create $PROJECT_NUM --owner @me \
--name "Swarm Status" \
--data-type "SINGLE_SELECT" \
--single-select-options "pending,in_progress,review,completed"
gh project field-create $PROJECT_NUM --owner @me \
--name "Agent Type" \
--data-type "SINGLE_SELECT" \
--single-select-options "coder,tester,analyst,architect,reviewer"
gh project field-create $PROJECT_NUM --owner @me \
--name "Priority" \
--data-type "SINGLE_SELECT" \
--single-select-options "critical,high,medium,low"
```
## 2. Task Synchronization
```bash
# Import issues with specific label to project
gh issue list --label "enhancement" --json number,title,url | \
jq -r '.[].url' | while read -r url; do
gh project item-add $PROJECT_NUM --owner @me --url "$url"
done
# Update item status based on issue state
gh project item-list $PROJECT_NUM --owner @me --format json | \
jq -r '.items[] | select(.content.type == "Issue") | "\(.id) \(.content.number)"' | \
while read -r item_id issue_num; do
STATE=$(gh issue view $issue_num --json state --jq '.state')
if [ "$STATE" == "CLOSED" ]; then
gh project item-edit --project-id $PROJECT_ID --id $item_id \
--field-id $STATUS_FIELD_ID --single-select-option-id $COMPLETED_ID
fi
done
```
## 3. Progress Tracking
```bash
# Get project progress summary
gh project item-list $PROJECT_NUM --owner @me --format json | \
jq '{
total: .items | length,
completed: [.items[] | select(.fieldValues[]?.name == "completed")] | length,
in_progress: [.items[] | select(.fieldValues[]?.name == "in_progress")] | length,
pending: [.items[] | select(.fieldValues[]?.name == "pending")] | length
}'
# Post progress comment to tracking issue
PROGRESS=$(gh project item-list $PROJECT_NUM --owner @me --format json | \
jq -r '"## Sprint Progress\n- Total: \(.items | length)\n- Completed: \([.items[] | select(.status == "Done")] | length)"')
gh issue comment $TRACKING_ISSUE --body "$PROGRESS"
```
## 4. Sprint Management
```bash
# Create sprint milestone
gh api repos/:owner/:repo/milestones \
-f title="Sprint 24" \
-f description="Sprint 24 - Jan 6-19, 2026" \
-f due_on="2026-01-19T23:59:59Z"
# Assign issues to sprint
gh issue edit 123 --milestone "Sprint 24"
gh issue edit 124 --milestone "Sprint 24"
# Get sprint burndown data
gh issue list --milestone "Sprint 24" --state all --json number,state,closedAt,createdAt | \
jq 'group_by(.state) | map({state: .[0].state, count: length})'
```Related Skills
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
tax-filing-session-setup-with-github-tracking
Structured workflow for preparing and tracking a tax filing session using prepared documents, task checklist, and GitHub issue cross-referencing
tax-filing-session-setup-with-github-traceability
Structured workflow for setting up a multi-file tax filing session with GitHub issue tracking and prepared-file validation
github-issue-structure-for-personal-finance-tracking
Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
github-actions-trigger-and-shell-gotchas
Prevent false verification gaps in GitHub Actions by checking push path filters, shell compatibility, and shared CI environment failures before concluding a workflow fix worked or failed.
github-actions-cross-platform-validation-gotchas
Execution-time GitHub Actions pitfalls discovered while fixing cross-platform CI workflows — path-filter non-triggers, Windows shell parsing mismatches, and job-scoped validation.
visual-review-board
Use when sourcing destination preview photos for a trip plan. Encodes the Wikimedia-API thumburl pattern (no hand-construction), main-session re-verification, and the destination-specific selection rule. Invoked by trip-planner.
github-visual-planning-issues
Create review-friendly GitHub planning issues that supersede stale/seasonal issues and include source-backed image thumbnails for faster human review.
github-roadmap-anchor-reuse
Reuse and reopen existing roadmap/epic GitHub issues instead of fragmenting work across duplicate replacement epics; retarget children and link active issues for continuity.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-pr-workflow
Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.