Problem statement lifecycle guide, skills, and label taxonomy rework - #14
Open
CelestialHoney wants to merge 10 commits into
Open
Problem statement lifecycle guide, skills, and label taxonomy rework#14CelestialHoney wants to merge 10 commits into
CelestialHoney wants to merge 10 commits into
Conversation
… ID lookup script Documents the six-status lifecycle on the A11y CoP Problem Statements Project (Not Ready through Artifact Delivered, or No Artifact Planned) and adds three skills to automate the repeatable steps: filing a new statement, advancing its status with the lifecycle's gates enforced, and the facilitator's post-session board reconciliation. Also updates README, CLAUDE.md, and the issue template to point at the new guide and skills. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…and Facilitator role Updates the Triage Process and Facilitator sections to describe the new lifecycle system (Not Ready through Artifact Delivered) and post-session board reconciliation, replacing the prior "labeled and selected" description that predated the A11y CoP Problem Statements Project. PENDING CoP AMENDMENT VOTE: per the charter's own Amendments section, this change requires a 2/3 member vote before it takes effect. Do not treat this commit as approved until that vote happens. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Removes labels superseded by the Status field and the new Discipline project field (status-duplicating, priority, outcome/resolution labels), renames strategic-theme labels under a theme: prefix, and adds a multi-select Discipline field for soft skill/expertise routing. Adds the using-gh skill documenting gh CLI's multi-select project field gap and the GraphQL workaround, plus a project-discipline-ids.sh helper mirroring the existing Status field script. Updates the lifecycle guide with a canonical label reference table and file-problem-statement with steps to set theme labels and Discipline at filing time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…e label
Move every gh command out of file-problem-statement/SKILL.md into a new
IMPLEMENTATION.md, leaving the skill as workflow and judgment only. Records the
project-field gotchas hit during real runs: --format json is required to get the
item ID, item-list reports multi-select fields as null, and multi-select
verification needs `options { name }`.
Drop the "[Problem] " title prefix and the `problem` label from the issue
template. Project membership is what marks an issue as a problem statement, and
unlike a hand-applied label it can't drift from the board. Lifecycle guide states
the trade-off: a repo-only issue view can no longer distinguish problem
statements without checking the board.
Add a context-gathering step before drafting, prompting the submitter for prior
discussion and any files worth reading, and specify that related-but-distinct
issues get a Related cross-reference in the body rather than a facilitator-only
note. Both came out of filing #18, which needed a second pass after prior
discussion surfaced constraints the first draft missed.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ield Introduces a Kind Project field (Problem Statement / Artifact) so artifacts built without a filed problem statement behind them can be tracked on the same board, entering directly at Artifact Planned. Adds the Artifact Submission issue template, a /file-artifact skill mirroring /file-problem-statement, and scripts/project-kind-ids.sh following the existing single-select field pattern. Named "Kind" rather than "Type" since GitHub Projects already has a built-in system field called Type. Kind is a Project field rather than a label, matching Status and Discipline — see docs/adr/0001-artifact-kind-as-project-field.md. Adds CONTEXT.md to disambiguate Problem Statement vs. Artifact vs. Kind going forward. Also updates every reference to the Project board's name, renamed from "A11y CoP Problem Statements Project" to "A11y CoP Artifacts Project".
Removes broken links to a never-committed ADR file, cleans up the charter's Triage Process to match the label taxonomy this PR introduces (drops the removed type/priority labels), and drops cop-board-review's reference to priority-* labels that no longer exist since there's currently no priority-tracking system. Also fixes file-problem-statement's asymmetry with file-artifact: it never explicitly set or verified the Kind field, relying on a "defaults to" framing that doesn't match how the board actually works — confirmed via GraphQL introspection that Project 21 has no workflow capable of auto-populating a custom field like Kind on item-add. Adds an explicit Set Kind and Status step mirroring file-artifact, and corrects "defaults to"/"defaulting to" phrasing across the lifecycle guide, CLAUDE.md, and the issue template to reflect that these fields are explicitly set, not automatic.
Collaborator
Author
|
The CoP voted in favor of the Triage Process / Facilitator role amendment in this PR (charter's 2/3-vote requirement per the Amendments section). Recording the outcome here since the amendment commit's message explicitly flagged it as pending: this can be merged as approved. |
… README skill count
using-gh claimed ProjectV2ItemFieldMultiSelectValue has no discrete list
field and can only be read as a comma-joined value string — contradicting
file-problem-statement and file-artifact, which both read Discipline back
via options { name } in their Verify Fields step. Confirmed via live schema
introspection and against a real project item: options { name } works and
returns discrete names. using-gh's error came from conflating this type
with the unrelated field-definition type ProjectV2MultiSelectField, whose
options really are under multiSelectOptions instead. Corrects SKILL.md and
IMPLEMENTATION.md to document options { name } as the way to read discrete
values, with the value string as a secondary option.
Also fixes README's "For Problem Statements" section, which still said
"Three Claude Code skills" and omitted /file-artifact after it was added.
…active branch Adds an explicit rule that Claude never runs git commit/push here without very direct, specific instruction naming that action — approval of the underlying content doesn't imply approval to commit. Also requires local changes stay reachable for review on the branch actually in use, not stranded in a separate worktree.
CelestialHoney
force-pushed
the
problem-statement-guide
branch
from
August 7, 2026 17:54
20660d7 to
0b1d4d5
Compare
Removes the placeholder --label flag from file-problem-statement and file-artifact's issue-create examples: omit it entirely when no theme fits (gh hard-errors on a nonexistent label) and show the repeated-flag syntax for two theme labels. Reworks cop-board-review's session-window detection, which inferred a reconciliation window from the two most recent session filenames and would silently narrow that window if a review ever got skipped. Now reconciliation cross-checks the latest session's notes against the board's current state, plus a full-board gate check that scans every item for lifecycle-rule violations regardless of session boundaries — neither depends on knowing when a review last ran, so no persisted marker file is needed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/problem-statement-lifecycle.md, three lifecycle-management skills (file-problem-statement,advance-problem-status,cop-board-review), andscripts/project-status-ids.shfor the A11y CoP Problem Statements Projecttheme:prefix; documents the canonical label set in the lifecycle guideusing-ghskill covering gh CLI's multi-select project field gap and the GraphQL workaround, plusscripts/project-discipline-ids.shTest plan
theme:*labels render correctly and match issues How to integrate accessibility into CI/CD pipelines and AI-assisted code review workflows #1, AI-enabled accessibility skill/tooling for automated issue detection #3, Advocating for Protected Time for Accessibility Work #5, A11y-focused UX research and validation #13's prior label assignments/file-problem-statementand confirm theme label + Discipline field can be set/advance-problem-status/cop-board-reviewagainst the current board🤖 Generated with Claude Code