dwoolworth
30 verified skills30 total stars
planning-board
Read tickets, post test result comments, and change ticket status as part of the QA gate on the Planning Board.
testing1
planning-board
Read review queue, post review feedback, and transition tickets through the CQ gate on the Planning Board.
databases1
planning-board
Read assigned tickets, post comments, and update ticket status on the Planning Board.
documentation1
meeting-board
Post status updates, respond to mentions, and communicate with the team on the Meeting Board.
tools1
images/qa/skills/test-runner
# QA Test Runner Skill ## Overview The test runner skill is how QA validates tickets against their acceptance criteria using real testing tools. You have two primary tools: **Playwright** (headless Chromium) for browser/UI testing and **curl + jq** for API testing. Every test follows a structured process: understand the criteria, determine the test mode, extract the target URL, execute the verification, capture evidence, document the result. ## Determining Test Mode Read the acceptance criter
tools1
images/po/skills/planning-board
# Skill: Planning Board (Full CRUD) PO has full, unrestricted access to the Planning Board. This skill covers every operation available: creating tickets, reading and querying tickets, updating any field, deleting tickets, assigning work, managing statuses, and reading comment and status histories. --- ## Configuration - **Base URL**: `${PLANNING_BOARD_URL}` (set via environment variable) - **Auth Header**: `Authorization: Bearer ${PLANNING_BOARD_TOKEN}` - **Content Type**: `application/json
documentation1
images/ops/skills/planning-board
# OPS Planning Board Skill ## Overview OPS has deployment-gate permissions on the planning board. You are authorized to read tickets, post deployment comments, and move tickets to their final `closed` status after successful deployment. ## Permissions | Action | Allowed | Notes | |-----------------|---------|-------------------------------------------------| | GET tickets | Yes | Filter by status, read all fields | | POS
devops1
images/ops/skills/meeting-board
# OPS Meeting Board Skill ## Overview The meeting board is where OPS communicates deployment status, infrastructure health, and coordinates with the team. Deployment transparency is critical -- the team should never have to guess what is deployed. ## API Usage ### Post a Message to a Channel ```bash curl -s -X POST "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "author": "ops",
development1
images/cq/skills/code-review
# Skill: Code Review This is CQ's core skill. Everything CQ does revolves around reviewing code changes and making a clear PASS or FAIL determination with actionable feedback. ## How to Review a PR ### Step 1: Gather Context Before reading a single line of code, understand what the change is supposed to do. 1. Read the ticket description and acceptance criteria on the planning board 2. Read all comments on the ticket for prior discussion and context 3. Note the PR/branch information from th
development1
images/ops/skills/deploy
# OPS Deployment Skill ## Overview The deployment skill covers the full lifecycle of deploying code to production: pre-checks, execution, verification, rollback, and documentation. Every deployment follows this process. No shortcuts. ## Pre-Deployment Checklist Before any deployment, verify ALL of the following: - [ ] **CQ Review passed:** Confirm a CQ approval comment exists on the ticket - [ ] **QA Testing passed:** Confirm a QA PASS comment exists on the ticket - [ ] **Ticket is in `rfp`
development1
code-review
Review code changes and PRs, making PASS or FAIL determinations with actionable feedback.
development1
deploy
Full deployment lifecycle including pre-checks, execution, verification, rollback, and documentation.
testing1
images/dev/skills/git-workflow
# Skill: Git Workflow ## Overview All code changes go through Git using a branch-based workflow. DEV never commits directly to `main`. Every change lives on a feature branch, goes through a pull request, and gets reviewed by CQ before merging. This skill covers the full workflow from cloning to PR creation. ## Configuration | Variable | Description | |-------------|--------------------------------------| | `REPO_URL` | Git remote URL for the repository | Git
development1
git-workflow
Branch-based Git workflow for code changes, commits, and pull requests.
development1
images/po/skills/human-comms
# Skill: Human Communication PO is the sole interface between the AI team and human stakeholders. This skill covers how to communicate with humans through the Meeting Board `#humans` channel, Discord webhooks, and Slack webhooks. --- ## Configuration | Environment Variable | Required | Description | |---|---|---| | `HUMAN_COMMS_TYPE` | No (default: `meeting-board`) | Communication channel: `meeting-board`, `discord`, or `slack` | | `HUMAN_COMMS_WEBHOOK_URL` | Only for `discord`/`slack` | The
development1
human-comms
Communicate with human stakeholders via Meeting Board, Discord, or Slack webhooks.
development1
images/cq/skills/meeting-board
# Skill: Meeting Board CQ uses the meeting board for team communication: participating in architecture discussions, reporting recurring quality patterns, and responding to direct mentions. ## Configuration - **Base URL**: Provided via the `MEETING_BOARD_URL` environment variable - **Auth Token**: Provided via the `MEETING_BOARD_TOKEN` environment variable - **All requests** must include the header: `Authorization: Bearer {MEETING_BOARD_TOKEN}` ## Channels CQ participates in the following ch
testing1
images/dev/skills/meeting-board
# Skill: Meeting Board Interaction ## Overview The meeting board is the team's shared communication space. Every persona uses it to coordinate work, discuss technical approaches, share status updates, and raise concerns. DEV has full read and write access to all channels. The meeting board is your primary tool for staying connected with the team. Use it to announce when you start work, when you submit for review, when you have questions, and when you need input on a technical approach. ## Co
tools1
images/qa/skills/meeting-board
# QA Meeting Board Skill ## Overview The meeting board is QA's communication channel with the rest of the team. Use it to post status updates, ask clarifying questions, report patterns, and respond to mentions. ## API Usage ### Post a Message to a Channel ```bash curl -s -X POST "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "author": "qa", "body": "Your message here" }' ``
development1
meeting-board
Participate in team discussions, report quality patterns, and respond to mentions on the Meeting Board.
testing1
meeting-board
Post deployment status, infrastructure health updates, and coordinate with team on the Meeting Board.
devops1
meeting-board
Post messages, run standups, monitor channels, and manage team communication on the Meeting Board.
tools1
meeting-board
Post test results, ask clarifying questions, and communicate QA status on the Meeting Board.
testing1
images/po/skills/meeting-board
# Skill: Meeting Board (PO — Enhanced Leadership Access) PO is the meeting leader. PO posts standup prompts, runs planning sessions, calls ad-hoc meetings, publicly calls out workflow violations, and monitors all team communication. This skill covers every Meeting Board operation available to PO. --- ## Configuration - **Base URL**: `${MEETING_BOARD_URL}` (set via environment variable) - **Auth Header**: `Authorization: Bearer ${MEETING_BOARD_TOKEN}` - **Content Type**: `application/json` A
data-ai1
images/cq/skills/planning-board
# Skill: Planning Board (CQ Gate Permissions) CQ uses the planning board as the primary interface for the code review pipeline. CQ's access is scoped to gate operations: reading the review queue, posting review feedback, and transitioning tickets through the gate. ## Configuration - **Base URL**: Provided via the `PLANNING_BOARD_URL` environment variable - **Auth Token**: Provided via the `PLANNING_BOARD_TOKEN` environment variable - **All requests** must include the header: `Authorization: B
development1
images/qa/skills/planning-board
# QA Planning Board Skill ## Overview QA has gate permissions on the planning board. You are authorized to read tickets, post detailed test result comments, and change ticket status as part of the QA gate in the pipeline. ## Permissions | Action | Allowed | Notes | |-----------------|---------|------------------------------------------| | GET tickets | Yes | Filter by status, read all fields | | POST comments | Yes | Detailed te
testing1
images/dev/skills/planning-board
# Skill: Planning Board Interaction ## Overview This skill covers how DEV interacts with the planning board to manage tickets through their lifecycle. DEV has LIMITED access to the planning board -- you can read your assigned tickets, update their status within allowed transitions, and add comments. You cannot create, delete, or reassign tickets. ## Configuration | Variable | Description | |-----------------------|------------------------------------| | `P
development1
planning-board
Read tickets, post deployment comments, and move tickets to closed status on the Planning Board.
devops1
planning-board
Full CRUD access to the Planning Board for creating, reading, updating, and deleting tickets.
tools1
test-runner
Run Playwright browser tests and curl API tests to validate tickets against acceptance criteria.
development1