cornerman

Plugin cornerman from marketplace bout-labs in BoutLabs/claude-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (10)

• bootstrap-project

  One-time conversational setup that detects the project stack, discovers GitHub Issue Types and project boards, writes `.claude/project.yaml`, and drops in starter CLAUDE.md, CONTRIBUTING.md, docs/, jtbd/, scripts/, AGENT_COMMS.log. Use once per new repo when installing cornerman. Idempotent — safe t

• cornerman-resume

  Full session-restoration skill. Builds on /cornerman where-am-i (#14) with the heavier "what's changed in main since work started", branch-vs-main file-overlap analysis, and rebase recommendations. Use when picking up work after days away, when returning from a context switch, or when the answer to

• cornerman-retro

  Aggregate cornerman telemetry, run manifests, and incidents into a markdown retro report. Read-only — no mutations. Surfaces where PRs stall, which contracts fail most, stuck issues, ci-fixer effectiveness, token outliers, recent watchdog incidents, and verification drift. Use when asked to "show re

• cornerman-where-am-i

  Per-issue resumability primitive. Reports last events, current tracker status, contract result per transition, latest run manifest, watchdog incidents, and a suggested next step — one screen, read-only. Auto-detects the issue from the current branch name. Use when picking work back up after a contex

• feature-impact-ranking

  Ranks open issues by user impact for "what to work on next" planning. Mutates the repo — leaves a resurface comment + impact-ranking label on each existing issue it surfaces, and creates a Feature issue for any net-new idea. Optionally accepts a count argument (default 5).

• research-competitive-scan

  Competitive-landscape scan for a product — what do adjacent apps offer that this product doesn't? Read-only research; does not file issues. Use standalone when you want a single methodology in isolation, or as the inline competitive step inside the `research-discovery` agent. Optionally accepts a to

• research-platform-scan

  Platform-capability scan — what APIs are under-adopted in this product's space and could differentiate it? Read-only research; does not file issues. Use standalone when you want a platform-only sweep, or as the inline platform step inside the `research-discovery` agent. Optionally accepts an area as

• research-signal-scan

  User-signal scan on a specific topic — App Store reviews of competitors, Reddit threads, niche communities, behavior research. Read-only research; does not file issues. Use standalone when you want raw user voice on a question, or as the inline signal step inside the `research-discovery` agent. Requ

• spec-context-gather

  Produce a research dossier for a feature topic — PRD section, JTBD persona, related open + closed issues, code surface map, prior art. Read-only; does not file or modify anything. Use before any product conversation to load context, or as the first step of writing a spec. Optionally accepts the topi

• spec-issue-file

  File a GitHub issue from a finalized markdown body with type / milestone / blocked-by / parent / labels / project-board placement set at create time. Reads project values from `.claude/project.yaml`. Mutates the repo. Use as the final step of `spec-writer`, or standalone for a hand-drafted body.

Slash commands (1)

• /cornerman:cornerman

  cornerman plugin housekeeping — version, upgrade, info. Use `/cornerman` with a subcommand (`upgrade`, `version`, `info`) to manage the installed plugin.

Subagents (11)

• architect

  Engineering architecture review of a hand-off-ready issue — the technical pass between `spec-writer` (product / scope) and `implementer` (tactical implementation). Reads the spec, reads the relevant code, and appends a `## Technical architecture` section to the issue body covering patterns to follow

• ci-fixer

  Diagnose and resolve a single failed CI run on a PR. Pulls the run log, classifies the failure (infra flake / compile / test / lint / merge conflict), locates the implicated code, and either applies a minimal mechanical fix in-place or files an issue / comments on the PR for anything bigger. Use whe

• evaluator

  Triage gate for raw `research-proposal` and similar pre-spec issues — judges each against PRD anchor, JTBD persona fit, milestone proximity, scope feel, and signal strength; applies `evaluated-keep` or `evaluated-cut` labels with a reasoning comment. Use when raw proposals have piled up in Backlog a

• ideation

  Conversational brainstorming partner — takes a fuzzy starting point ("what should we ship next?", "I've been thinking about X", a JTBD persona, a constraint) and produces 3–7 raw ideas with cited reasoning, ready to file as `research-proposal` issues for the `evaluator`. Use when the human wants to

• implementer

  End-to-end implementation of a single hand-off-ready issue — branch off the project's default branch, write the change, run the stack's pre-push gate (format / lint / test), push, open a PR with `Closes #N`. Stops at PR-open; merging follows the project's merge policy. Stack-agnostic — reads command

• learnings-extractor

  Fires after a CI failure investigation (ci-fixer exit) or a PR merge. Identifies new project-specific gotchas worth remembering, writes them to the project's docs/LESSONS.md with provenance + quarantine + expiry. Read-and-write — but only against docs/LESSONS.md; never modifies the agent prompts the

• post-merge

  Fires automatically on PR merge. Refreshes blocked-by state on downstream issues, drafts a CHANGELOG entry, archives the worktree, prunes the branch, and pings learnings-extractor. Small, high-frequency annoyance killer per #18. Each action is independently togglable per project under `cornerman.pos

• pr-reviewer

  Independent pre-merge code review of a PR opened by `implementer` (or any agent / human). Runs after the implementer pushes — reads the diff, checks against the issue's spec + the architect's guidance, posts a structured review on the PR via `mcp__github__pull_request_review_write` with blocker / su

• qa-tester

  QA gate between implementer's PR-open and pr-reviewer. Runs project-defined scenarios in a real-ish environment (simulator, dev server, smoke endpoint) via per-stack runners. Posts evidence (screenshots, logs, pass/fail status) as a PR comment. Skips cleanly when the stack lacks a `qa_runner` capabi

• research-discovery

  Surface net-new feature ideas from outside the existing roadmap — competitive landscape, platform capabilities, behavior research, App Store / Reddit signal. Conversational loop with a final gate before filing each surviving idea as a `research-proposal`-labeled Feature issue. Use when the human wan

• spec-writer

  Turn a fuzzy idea into a hand-off-ready Feature/Task/Bug issue with type, milestone, blocked-by, parent, acceptance criteria, file list, and project-board placement set at create time. Use when there's an idea but no issue, or an issue body too squishy for the implementer to act on. Do NOT use for r

Similar plugins