Justin Black
Community@blac9216
Justin Black maintains six skills for issue-driven GitHub repository management, covering planning, owner interrogation, architecture documentation, PR review, and board configuration.
Agent Skills by Justin Black
Showing 6 vetted skills indexed across 1 GitHub repositories.
blac9216plan-work
Decompose feature asks into GitHub milestones, epics, and estimated issues with projected timelines.
blac9216interrogate
Interrogate owners about plans through structured question rounds and produce decision records.
blac9216design-docs
Adopts, authors, and audits a repository's ADR, rationale-index, and Diátaxis documentation standard.
blac9216github-pr-review
Reviews GitHub pull requests adversarially and squash-merges them after verification.
blac9216github-workflow
Orchestrates issue-driven GitHub workflows across project boards, milestones, epics, and pull requests.
blac9216configure-workflow
Configures and audits GitHub repositories for the github-workflow skill's Project boards, labels, and rulesets.
Frequently Asked Questions About Justin Black
FAQPage SchemaWhat tasks can I accomplish with blac9216's skills?▼
You can plan and decompose work into milestones, epics, and estimated issues; interrogate designs into decision records; set up ADR, C4, CONTEXT.md, and Diátaxis documentation; run issue-driven GitHub board execution; independently review and merge PRs; and configure or audit repository boards, labels, and branch rulesets.
Who are these skills designed for?▼
They target repository owners and maintainers running an issue-driven GitHub process organized as Project board, delivery-story milestones, domain epics, and issues. They suit solo operators or orchestrators of parallel subagents who want planning, documentation, and review discipline enforced from the first commit.
How do the skills work together in practice?▼
configure-workflow prepares the board, labels, and rulesets; plan-work turns asks into milestones and issues; interrogate resolves open decisions; design-docs records them as ADRs and rationale; github-workflow executes issues through branching and PRs; github-pr-review independently verifies and squash-merges the result.
What are the prerequisites for using these skills?▼
You need a GitHub repository, ideally configured via configure-workflow with a Project board, canonical and area labels, branch rulesets, and docs/process files. PR review uses GitHub MCP tools in a cloud sandbox or the gh CLI locally. plan-work works on any repository but is best on a configured one.
Is configure-workflow safe to run repeatedly on an existing repository?▼
Yes. configure-workflow is explicitly idempotent, so re-running it is safe. It supports apply, audit, and capture modes to set up fresh repos, repair drifted labels or missing fixtures, and snapshot an edited Project board as the new standard template.