Configures a GitHub Project board through the Chrome MCP: creates the kanban status columns and switches the view to a Status-grouped board, then refreshes pscode/github.yaml. Use it from /ps:board-setup, typically right after init creates a new Project.
Finalizes a change: writes a short openspec-style delta spec, archives the change under pscode/changes/archive/<date>-<slug>/, and syncs the board to Done. Also handles the cancel path (card → Cancelled). Use it from /ps:complete and /ps:cancel.
Develops a refined change: moves the card to In Development, implements the refine.md subtasks one at a time on the current branch, then walks the card through Code Review → Test → Ready to Deploy. Use it from /ps:dev.
Keeps the GitHub Issue, board status, assignee, comments in sync with the guided flow, using gh. Use it from every /ps:* step when pscode/github.yaml exists. Every gh call is non-blocking.
Interrogates a request before implementation — objective questions that reduce ambiguity, at most 5, asked through AskUserQuestion (structured choices + free-text), recorded in questions.md. Use it to validate understanding before writing specs or code.
Drives a change through four short, human-validated steps that mirror the board: draft → refine → dev → complete. Use it to guide any change from start to finish.
Writes or revises a short brief.md: objective, expected behavior and out of scope, in plain language. Use it to turn understanding into a small, approvable spec.
Refines a Backlog draft into an issue-ready document: claims the card (In Refinement), analyzes the code, runs Grill Me, writes a standardized refine.md (summary, technical detail, scope, subtasks), then moves the card to Ready to Dev. Use it from /ps:refine.