nguyenvanphituoc
UserShape Up for coding agents — with gates the agent can't talk its way past. A Claude Code plugin that runs idea → pitch → build → eval → ship, with PreToolUse hooks that hard-deny a premature EVAL and progress derived from test artifacts instead of self-report.
Categories
Indexed Skills (15)
architecture-research-report
Research a technical question deeply, then produce an evidence-dense architecture report that takes a position, shows its work, and carries Mermaid diagrams and comparison tables. Writes as a solution/systems architect and senior AI/data engineer would: leads with the finding, grounds every claim in a citable source (file:line, benchmark number, doc §-reference), costs the recommendation, claims the negative space, and names what would change the answer. Use this whenever the user asks to evaluate or compare technologies, vendors, or architectures ("Kafka or Kinesis?", "which vector DB for our RAG stack?"); analyze, review, or reverse-engineer an existing system or codebase's architecture; research the state of the art in a technical domain; write a design doc, tech brief, architecture review, or ADR-scale analysis; or asks for "insights", "perspective", "a deep dive", "a report", or diagrams on a technical topic — even when they never say the word "report". Also use for reviewing AI/agent/LLM system architec
harness-maintenance-audit
Audit this plugin repo for two kinds of rot: documentation that no longer matches the shipped plugin, and internal bookkeeping that has leaked into files users receive. Derives every fact from the artifact itself — enums from the schema, counts from the filesystem, hook behavior by executing the hook — then fixes the docs and reports code defects separately. Use this whenever maintaining this repository: before a release or version bump, after removing/renaming/adding a skill, operation, hook or command, after any commit that touches `skills/`, `hooks/`, `commands/`, `schemas/` or `docs/`, and whenever the user asks to "check the docs are current", "audit for drift", "make sure the plugin is clean", "does the documentation match", "is anything out of date", or wants a consistency/parity check between code and documentation. Also use it proactively before committing a refactor that deletes or renames anything, because the blast radius of a cleanup commit is routinely wider than its message claims.
plan-executor
Execute a staged plan document end to end — compile its recommendation into an acceptance contract, implement each stage, verify every one in a fresh git clone, and on failure freeze the evidence, diagnose it from three independent angles, apply the best admissible fix and re-verify from a clean state, looping until the plan is green or the budget runs out. Use this whenever the user points at a plan, review, report, ADR, design doc or issue and asks to "execute it", "run this plan", "make this happen", "carry out the recommendation", "do §6", "make the acceptance tests pass", or "keep fixing and re-running until it's green" — including when they just paste a path to a document with a staged recommendation and say go. Also use for long unattended runs that must survive usage limits and resume, and for any request to auto-fix failures found while executing a plan rather than stopping at the first red. If no plan document exists yet, produce one first with the architecture-research-report skill, then execute it
ba-pitch-analyzer
Use this skill whenever a user provides a product requirement, pitch, or feature description and wants it broken down into structured, executable development tasks. Triggers on: "analyze this pitch", "break this into tasks", "generate tasks from requirement", "act as BA", "create spec from PRD", "turn this into dev tasks", or any request to decompose a feature into DDD-structured documents and tasks; also on Shape Up, bounded context, domain model, or use cases, and on a tech-lead --order dispatch. Produces a linked pitch → domain model → use cases → tasks document tree with BDD scenarios and a derived Test Surface.
coach
Use this skill to turn raw Product Owner / Tech Lead feedback at the Ship Sign-off (L4 Gate) into structured, team-shared guidelines that future harness runs read back. Triggers on: "coach this feedback", "record this for next sprint", "update the knowledge base", "RLHF the harness", and Vietnamese "ghi lại cho sprint sau", "cập nhật knowledge base". tech-lead invokes it automatically at GATE L4 when the PO gives substantive feedback instead of a bare 'y'. NOT for grading work (spec-evaluator), fixing bugs (task-executor), or filing discovered tasks (the ledger).
orient
Use this skill for Shape Up step 7 (Orient) — the builder-led reconnaissance pass that runs AFTER kick-off and BEFORE any task board exists. Triggers on: "orient on this feature", "scout the codebase for this pitch", "where does this pitch touch the code", "do an orient pass", "recon before we plan", "spike the riskiest part before mapping scopes". The tech-lead orchestrator invokes it at step 7 before delegating to ba-pitch-analyzer (Map Scopes, step 8). Use it even when the user describes "read the code first and surface the unknowns" without naming Orient. Also accepts a tech-lead --order dispatch.
qa-edge-hunter
Use this skill for the post-PASS exploratory QA pass — Shape Up's "QA is for the edges", made explicit for the harness. Triggers on: "hunt edge cases", "QA pass on this feature", "exploratory test the running app", "edge hunt before ship", "run qa-edge-hunter", "the evaluator passed — what did it miss?". tech-lead invokes it after the run's first PASS at GATE L3, before SHIP; it also runs standalone given a spec folder, a PASS EVAL report, and a running app, or on a tech-lead --order dispatch. It charters edges OUTSIDE what the evaluator probed and hunts them through six fixed lenses. NOT for checking AC (spec-evaluator), deriving test cases (ba), or fixing bugs (task-executor).
scope-architect
Use this skill to map the vertical scopes of a feature — Shape Up's "map the scopes" (step 8) as committed, mechanically enforceable contracts. Triggers on: "map the scopes", "write the scope contracts", "scope contract", "the discovered tasks don't fit any scope", "re-slice the substrate" (operations map-scopes). Writes the committed scopes/*.md contracts by import-graph slicing along business flow, with write-whitelist substrates and e2e fixtures. NOT for decomposing a pitch into tasks (ba-pitch-analyzer) or cutting scope at ship time (scope-hammer).
scope-hammer
Use this skill whenever a Shape Up build run reaches its stop condition — the circuit breaker (round budget or a scope's attempt budget) trips, or all scopes finish and it's time to decide when to stop (step 11) — and needs a must-have census, a baseline-anchored cut list, and a ship verdict. Trigger on: "scope hammer", "hammer this down to must-haves", "decide when to stop", "cut list vs baseline", "circuit breaker tripped, what do we ship", "compare against the baseline not the ideal", "GATE H", "census the open items". Also triggers on tech-lead's GATE H at SHIP. Compares the product to the pitch's baseline (what customers live with today, not a perfect ideal) and returns a cut list + ship verdict.
shapeup
Use this skill for any Shape Up workflow before writing code. Triggers on: "shape this feature", "frame this problem", "breadboard this", "map affordances", "write a framing doc", "write a kickoff doc", "turn this transcript into a framing document", "turn this transcript into a kickoff document", "what should we build", "explore solutions", "is this shaped enough to build", "slice this into scopes", "fit check", "wiring diagram". Also triggers when user says "before we build...", "I want to think through...", "let's shape this", or provides a raw transcript and wants it structured. DEFAULT: if no sub-command given, run /shapeup full — ask clarifying questions at each gate, keep solutions as simple as possible, never touch parts that already work. Sub-commands: /shapeup full | /shapeup shaping | /shapeup spike | /shapeup breadboarding | /shapeup framing-doc | /shapeup kickoff-doc | /shapeup breadboard-reflection
solution-architect
Use this skill to design how each use-case's engine integrates into the running application — the wiring map that guarantees no engine ships orphaned. Triggers on: "write the wiring map", "declare the integration seam for each use case", "how does each use case get wired in", "map engines to the entry point", "which use cases are reachable from the composition root", "the asset pipeline has zero call sites", "front-load the integration seam before we slice scopes", or a tech-lead --order dispatch (operation wire) at gate L1a.5. Writes the per-use-case wiring map: engine → integration seam → composition-root attachment → player-visible affordance, resolved against the project profile's entry_point. NOT for slicing scopes (scope-architect) or decomposing a pitch into tasks (ba-pitch-analyzer).
spec-evaluator
Use this skill whenever the user wants to evaluate, QA, or verify that an implemented task actually matches its spec and acceptance criteria — the judge in a planner→generator→evaluator harness. Trigger on: "evaluate task TASK-NNN", "QA TASK-NNN", "verify against spec", "check acceptance criteria", "does this match the spec", "grade this build", "run evaluator", or a tech-lead --order dispatch. Skeptical by default — absence of evidence is a FAIL; probes the running app and files file:line bugs.
task-executor
Use this skill whenever a user wants to execute, implement, or run a specific task generated by the ba-pitch-analyzer skill. Triggers on: "execute task TASK-NNN", "implement TASK-NNN", "run this task", "start working on TASK-NNN", "implement the task in [folder]", "run task from spec folder", "pick up the next task", or a tech-lead --order dispatch. Implements a task's acceptance criteria exactly — minimum code, surgical diffs, verified observable outcomes.
tech-lead
Use this skill whenever the user wants to orchestrate a whole feature end-to-end across the harness skills — ba-pitch-analyzer (planner), task-executor (generator), spec-evaluator (judge) — acting as the tech lead that owns the run and reports to the PO at round boundaries. Trigger on: "run the full harness", "act as tech lead", "ship this feature end to end", "from pitch to ship", "orchestrate the build", "plan build evaluate". Use it even when the user describes a multi-step build flow without naming the skills.
translator
Use this skill whenever intake for the harness (pitch, PRD, requirement, transcript, or any spec input) is in a non-English language and must be normalized to English BEFORE planning/building. The single language gate for the planner→generator→judge harness. Triggers on: "translate this pitch", "normalize to English", "this requirement is in Vietnamese", "prepare intake for the harness", "make the spec English", "check if this is English", and Vietnamese "dịch sang tiếng Anh", "chuẩn hoá tiếng Anh", "dịch pitch", "chuyển yêu cầu sang tiếng Anh". Produces faithful English copies (original never overwritten) plus a glossary and verification report. tech-lead auto-invokes it at GATE L0 when intake is non-English; also runs standalone.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.