digital-agency-plugins

Instance bootstrap interview — detects existing instance state, guides repo creation (link-first), interviews business identity/services/cadence/targets, writes config/instance.json and target skeletons, then hands off to brand-creative setup. Use on first install, when the user says "set up my instance" or "bootstrap my agency workspace", or to re-check target bindings after config changes.

Create a competitive analysis brief for product strategy, feature prioritization, or sales enablement. Use when comparing competitors, mapping a feature area across rivals, or drafting battle cards. Do NOT use for user research synthesis (synthesize-research) or product strategy doc (product).

Run a weekly, monthly, or quarterly metrics review: scorecard, trends, bright spots, concerns, and recommended actions. Use when investigating a spike or drop, comparing performance against targets, or preparing a metrics readout. Do NOT use for stakeholder status updates (stakeholder-update) or product strategy (product).

Sparring partner for exploring a problem space, generating solutions, or stress-testing product thinking. Conversation, not a deliverable. Use when ideating, assumption-testing, or strategy exploration before a spec. Do NOT use for writing specs (write-spec) or product strategy doc (product).

Write a weekly or monthly status for leadership, announce a launch, escalate a risk, or tailor the same progress for exec, engineering, partner, customer, or board audiences. Use when drafting status updates or launch notes. Do NOT use for product strategy (product) or roadmap updates (roadmap).

Synthesize interview notes, survey data, or support tickets into themes, personas, opportunity areas, and roadmap recommendations. Use when turning raw research into structured findings. Do NOT use for competitive analysis (competitive-brief) or product strategy doc (product).

Turn a feature idea or problem statement into a structured feature spec or PRD with user stories, requirements, and success metrics. Use when drafting a PRD, feature spec, or requirements doc. Do NOT use for product strategy doc (product), epic task breakdown (tasks), or roadmap phasing (roadmap).

Review content seed PRs for on-page SEO — titles, meta descriptions, heading structure, keyword usage, and internal linking. Use when reviewing seed JSON or draft content before merge. Produces PR review comments only. Do NOT use for technical site audits (technical-seo-audit) or drafting content (draft-post).

Research keywords for a topic area — search intent, volume signals, and content opportunities. Use when planning content around a topic or building keyword targets for the calendar. Writes `.agency/work/seo/keyword-research-{topic}.md` on the target repo. Do NOT use for technical site audits (technical-seo-audit) or competitive product analysis (competitive-brief).

Audit production SEO — metadata, canonical/OG, sitemap, robots, structured data, and Core Web Vitals signals. Use when auditing a live site or filing SEO recommendations. Creates GitHub issues labelled `type:seo-recommendation` with owning squad. Do NOT implement fixes — hand to engineering squads.

Produce a low-fidelity layout and interaction spec from a brief. Use when the user names a page or flow and wants a wireframe before implementation. Writes `<design-dir>/{page-or-flow}.md` (resolve path per ux-design-conventions.md). Reads brand-guide.md when present. Do NOT use for epic technical design (design), visual brand tokens (brand-guide), or code implementation (implement).

Investigate bugs, errors, or unexpected behaviour — reproduce, isolate, diagnose, and fix. Use when given an error message, stack trace, "works in staging but not prod", or "broke after deploy". Do NOT use for incident response workflows, code review (code-review), or implementation (implement).

Prepare a QA workspace — checkout a branch or MR ref, install dependencies, and verify the environment is ready for test execution. Use before running automated or exploratory QA. Do NOT use for running tests (run-automated-suite), exploratory validation (exploratory-pass), or fixing code (implement).

Structure reproducible defect reports from failed QA output — automated suite failures, exploratory gaps, or combined validation results. Use when turning test output into a defect table. Do NOT use to fix code (implement) or re-run tests (run-automated-suite).

Acceptance-criteria-driven exploratory validation in a prepared QA workspace — manual-style checks, browser verification, or CLI probes against tasks.md Gherkin. Use after deploy-qa when exercising AC. Do NOT use for automated tests only (run-automated-suite) or defect formatting (document-defects).

Final technical gate on an open PR or MR after peer review — architecture boundaries, security, and acceptance-criteria coverage against `.agency/work/{epic}/tasks.md`. Use when the MR is open and CI is expected green. Do NOT use for pre-PR peer review (code-review), business stakeholder sign-off (validate), or implementation (implement).

Audit platform health — dependency updates, uptime, error rates, CI status, and deployment hygiene. Use for "dependency audit", "check Sentry errors", "platform health review", or scheduled maintenance. Do NOT use for feature implementation (implement) or debugging a single bug (debug).

Run the project's automated test suite in a prepared QA workspace. Use after deploy-qa when executing CI-equivalent tests. Do NOT use for workspace setup (deploy-qa), manual AC checks (exploratory-pass), or fixing failures (implement).

Identify, categorize, and prioritize technical debt. Use for "tech debt audit", "what should we refactor", "code health", or refactoring priorities. Do NOT use for code review (code-review), architecture decisions (adr), or bug investigation (debug).

Analyse image or video media into structured tags: subjects, season, mood, content type, alt text, description, and quality score. Use when tagging media for content pipelines, or when the user asks to analyse an image or video for social or CMS. Reads brand and taxonomy from the resolved brand path. Do NOT use for writing captions (write-captions) or selecting posts (curate-content).

Rank assets from an approved media inventory for upcoming social posts. Use when selecting what to post next, curating from inventory JSON, or choosing seasonal assets. Reads brand from the instance repo. Do NOT use for analysing a single image (analyse-media) or writing captions (write-captions).

Draft a blog post seed JSON for CMS import at the target repo's resolved post seed path, with body as markdown. Use when writing a blog seed from a calendar brief or slug. Match brand-voice.md before finishing. Do NOT merge or publish — seed PR only. Do NOT plan the calendar (content-calendar) or run SEO review (content-seo-review).

Draft a recipe seed JSON for CMS import at the target repo's resolved recipe seed path, with structured-data fields (times, servings, difficulty). Use when writing a recipe seed from a calendar brief or slug. Match brand-voice.md before finishing. Do NOT merge or publish — seed PR only. Do NOT plan the calendar (content-calendar) or audit site-wide structured data (technical-seo-audit).

Review caption variants and select or lightly edit the best one for publication. Use when choosing among write-captions output, editorial caption review, or polishing a final caption. Reads brand voice from the instance repo. Does not append hashtags. Do NOT use for initial caption generation (write-captions).

Write Instagram caption variants and channel copy from media tags or analyse-media output. Use when drafting social captions, Google Business copy, or email teasers from tagged media. Reads brand from the instance repo. Do NOT use for selecting the final caption (edit-content) or vision analysis (analyse-media).

Content marketing practice setup interview — reads instance business identity and house tone hints from `/agency-hub:setup`, interviews content cadence, primary channels, distribution connectors, and persona preference (Content Strategist vs Content Writer vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up content" or "configure editorial calendar", or to redo content defaults only.

Use when the user wants ADR register planning, writing ADR-NNNN files, or ADR review under .agency/architecture/decisions/. Triggers on "do we need an ADR", "write ADR-0007", "record this decision", "what decisions need making", "harvest ADRs from this epic". Do NOT use for full architecture narrative (solution), epic design (design), or product strategy (product). Proposals stay in register.md only until accepted.

Use when the user wants to address, action, or fix findings from a code review — their own working diff reviewed by code-review, a reviewer's comments on a PR or MR, or a pasted list of issues. Triggers on "fix the review findings", "address the review feedback", "action the blocking issues", "apply the review comments". Optionally scoped to an action tier (blocking, warning, all). Makes targeted, behaviour-preserving changes, runs the project's validation suite, and commits in logical units. Do NOT use to perform a review (code-review), to implement new work or features (implement), to address UX or design-fidelity findings (ux-design-review), or to open a PR/MR (merge-request).

Use when the user wants a code review of a branch, PR, MR, or working diff against its acceptance criteria and declared scope, in whatever form they take in this repo. Triggers on "review my branch", "review this PR", "check this diff before I raise it", "is this ready to merge". Works with any language, delivery process, or issue tracker. Produces a structured verdict with blocking, warning, and suggestion findings; writes no source changes. Do NOT use to address or fix review findings (code-review-fix), to implement work (implement), to publish a review to a provider as its reviewer (merge-request-review), to sign off completion of a larger body of work (validate), or to review rendered UI (ux-design-review).

Use when the user wants epic-level technical design at .agency/work/{epic}/design.md, walking-skeleton or TDD design, or design review before tasks. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Triggers on "design CHK01", "write the epic design", "how should we build this epic", "review the design before tasks". Do NOT use for epics or stories (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), code implementation (implement), or reviewing a set of documents for quality and consistency (docs-review).

Use when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive. Triggers on "review the docs", "are these docs any good", "is our documentation consistent", "do these docs overlap", "audit the documentation". Works on any doc set in any format or tool. Read-only: produces a report and changes nothing. Do NOT use to write or amend a document, to review code (code-review), or to review rendered UI (ux-design-review).

Use when the user wants to implement a task in code against an approved design.md and .agency/work/{epic}/tasks.md. Triggers on "implement CHK01-01", "build this task", "write the code for this story". Reads the design and acceptance criteria, writes code and tests, runs the project's full validation suite, and commits in logical units. Do NOT use for code review (code-review), addressing review feedback (code-review-fix), changing how existing UI looks or behaves (ux-design-fix), writing tasks (tasks), or writing a design (design).

Use when the user wants an already-open merge request or pull request driven to a merge-ready state — watching CI, fixing objective check failures, triaging review threads, and syncing merge conflicts until all checks are green and nothing is unresolved. Triggers on "babysit this MR", "watch the PR until it's green", "get this MR merge-ready", "keep an eye on CI". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Never merges. Do NOT use to open an MR (merge-request), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement new work (implement).

Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Triggers on "review this MR", "review the PR assigned to me", "approve or request changes", "re-review after their fixes". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).

Use when the user wants to open a merge request or pull request for the current branch, with a generated title, description, labels, and reviewer suggestions. Triggers on "open a PR", "raise an MR", "create a pull request", "put this branch up for review". Resolves change context and provider, discovers the repo's MR/PR template, composes a size-adaptive description, pushes, and creates the MR. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to drive an open MR to merge-ready (merge-request-babysit), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement changes (implement).

Use to seed or configure a Ralph loop before running it: choose a preset (engineering delivery for an epic, ad-hoc for a single repeating prompt, or custom steps), resolve the environment, set the completion promise and iteration budget, and write the loop files. Triggers on "set up a ralph loop", "configure a ralph loop", "ralph-loop-setup", or naming an epic to loop over. Do NOT use to start, inspect, or stop a loop (ralph-loop) — setup never executes loop steps.

Use to start, inspect, or stop a Ralph loop: an autonomous self-referential loop where a stop hook re-feeds the same prompt every turn until a completion promise is emitted or a safety rail fires (ralph-loop start, ralph-loop status, ralph-loop cancel). Works for any repeating multi-step job via presets, including full epic delivery through implement, review, validate, and merge request. Do NOT use to seed or configure a loop (ralph-loop-setup), implement a single task once (implement), review a diff (code-review), or sign off an epic (validate) — the loop orchestrates those skills.

Web development practice setup interview — detects or creates .agency/target.json binding, reads instance profile from `/agency-hub:setup`, interviews tech stack, deployment platform, connectors, and persona preference (six engineering personas vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up web development" or "bind target repo", or to redo engineering defaults only.

Use when the user wants to write or review system architecture at .agency/architecture/solution.md (stub or full arc42-lite). Triggers on "write the architecture", "solution design", "arc42", "review the architecture", "does solution.md match what we built". Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in .agency/work/{epic}/tasks.md.

Use when the user wants to change how existing UI looks or behaves — fix spacing, colour, layout, states, responsiveness, or accessibility on a component, page, or flow. Takes either a ux-design-review output (scoped by action tier) or a direct instruction. Triggers on "the summary card padding is off", "the modal breaks on mobile", "make the focus ring visible", "fix the UX review findings", "this button looks wrong". Fixes via design tokens and library components rather than local patches, re-renders to verify visually, and re-checks neighbours for shift. Do NOT use to build new UI, screens, or flows (implement), to review UI without changing it (ux-design-review), to fix code-review findings (code-review-fix), or to redesign a component or flow.