Results for “artifact-triage”

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Create, retrieve, query, and update Artifacts — tangible deliverables produced by the project. Use when storing or retrieving documents, designs, datasets, build outputs, slide decks, or any completed deliverable that should be registered in the project catalog.

Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

Decide, before an expensive workflow runs, whether an artifact needs a full rebuild, a partial refresh, a skip, or a recycle. Inspects how old the artifact is and what actually changed underneath it, then returns a section-by-section plan with the token and cost savings. The cheap gate that keeps expensive generation from running on data that did not move. Built for anyone running repeatable AI workflows, customizable to your artifacts and your data sources. Trigger on "should we regenerate this", "refresh the report", "is this still fresh", "what needs updating", "when was this last run", "do we have a fresh brief", or any artifact-refresh question.