guild

Plugin guild from marketplace hirokata in HirogaKatageri/hirokata. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• brief

  This skill should be used when the user asks for "guild status", "board status", "what's the status", "show the board", "what's on the board", "project status", "show guild", "guild board", "what's happening", "brief me", "guild brief", "where are we", "what changed", "what moved since last time", "

• check-in

  This skill should be used when the user says "check in", "clock in", "standup", "guild check in", "let's get to work", "start working", "continue working", "daily standup", "guild standup", "I'm here", "reporting in", or any phrase indicating they want to begin or resume a guild work session. Acts a

• comprehensive-review

  Use this skill when the user wants to review code changes, verify implementation quality, or check readiness before a PR or deployment. Trigger on phrases like "review my changes", "run comprehensive review", "check all my code", "am I ready for PR", "before I create a PR", "before I merge", "code a

• create-workflow

  This skill should be used when the user asks to "create a workflow", "generate a workflow", "add a GitHub Actions workflow", "create a CI/CD pipeline", "write a script workflow", "automate a task", "set up automation", or wants to build any kind of automated workflow (GitHub Actions, Python scripts,

• dashboard

  This skill should be used when the user asks for "the dashboard", "guild dashboard", "open the dashboard", "show me the dashboard", "build the dashboard", "visualize the board", "the roadmap", "show the roadmap", "a visual view of the guild", "the coverage view", "the activity feed", or wants to see

• domain-software

  The SOFTWARE domain profile for the strategist. A domain profile answers the six questions the strategist's method deliberately leaves open: what surveying the current state means, what two concurrent tickets contend for, which capabilities the work routes to, what sections a plan carries, what sect

• new-requirement

  This skill should be used when the user asks to "add a requirement", "new requirement", "I need a feature", "add to the guild", "create requirement", "queue a feature", "I want to build", or wants to add a new work item to the guild board. Runs a live interview between the project-manager and the us

• qa-artifacts

  Pre-loaded QA artifact reference for the qa-strategist and qa-tester agents. Says which QA output is a DATABASE ROW (defects in the `bug` table, quality areas in the `coverage` table) and which stays prose under `.guild/qa/` (charter, missions, session logs, regression manifest) — with the exact SQL

• qa-mindset

  Pre-loaded QA discipline for the qa-strategist and qa-tester agents. Covers the five QA pillars (validation over verification, disconfirmation, empiricism, the oracle problem, risk-based triage), the hybrid oracle rule for testing existing products, the layered oracle resolution order, the what-if i

• qa

  This skill should be used when the user wants quality assurance on the product itself — "QA the product", "QA the checkout flow", "run a QA pass", "build comprehensive e2e tests", "write regression tests", "test the running app", "what-if testing", or any request to empirically test the product and

• release

  This skill should be used when the user asks to "cut a release", "release the guild", "ship it", "create a release", "tag a version", "publish a release", "guild release", or wants to finalize completed requirements into a versioned release. Renames CHANGELOG Unreleased to a version, records the rel

• shift

  This skill should be used when the user asks to "work a shift", "run unattended", "keep working while I'm away", "guild shift", "take the night shift", "work the board while I'm out", "run autonomously", "keep going without me", "work overnight", "run until you need me", or any request for the guild

• svelte-advanced

  Pre-loaded advanced Svelte 5 / SvelteKit techniques for the developer-svelte agent. Covers attachments ({@attach}), actions (use:), transitions and animations, the motion module, custom elements, packaging libraries, server hooks, remote functions, service workers, shallow routing, and view transiti

• svelte-best-practices

  Pre-loaded Svelte 5 / SvelteKit best practices for the developer-svelte agent. Covers state management strategies, performance optimization, accessibility, SEO, TypeScript usage, testing (vitest + playwright), and error handling. Load alongside the other svelte-* skills before implementing anything

• svelte-build-deploy

  Pre-loaded SvelteKit knowledge for the developer-svelte agent. Covers project structure, file-based routing (+page, +layout, +server, +error), load functions (universal vs server), form actions, page options (prerender / ssr / csr), building for production, and deployment via adapters (auto, node, s

• svelte-core

  Pre-loaded Svelte 5 core knowledge for the developer-svelte agent. Covers the component model, runes ($state, $derived, $effect, $props, $bindable), basic markup, control flow, snippets, bindings, scoped styles, lifecycle, and context. Load this skill before writing or editing any .svelte, .svelte.t

• svelte-env-vars-check

  This skill should be used when the user says "check svelte env vars", "check environment variables", "validate env vars", "check env var patterns", "audit environment variables", "audit env vars", "check SvelteKit env", "svelte env check", or any phrase asking to audit or validate SvelteKit environm

• validate

  This skill should be used when the user asks to "validate the guild", "check the guild", "does this match expectations", "run the expectations", "validate the board", "check the invariants", "verify the board", "did that actually land", "check the board against expectations", or wants to know whethe

• verify-and-fix

  This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found a bug", "got an error", "debug this", "th

• warehouse

  The guild's warehouse — how to read and write guild data with SQL. Load this before touching anything in the guild database: tasks, requirements, plans, goals, projects, bugs, review findings, work logs, coverage, the execution graph, gates, ticket capabilities, or the event feed. Also load it for t

Subagents (15)

• developer-svelte

  Use this agent when the guild needs code implementation in a Svelte or SvelteKit web application. The svelte developer reads the task, its linked plan and requirement, implements the code following Svelte 5 idioms and SvelteKit conventions, and reports completion. Spawned by the check-in skill when

• developer

  Use this agent when the guild needs code implementation. The developer reads the task, its linked plan and requirement, implements the code, and reports completion. Spawned by the check-in skill when an implementation task is on the board.

• librarian

  Use this agent when the guild needs the finished work written down — what the business rules ARE, how a subsystem now works, and which decisions the requirement actually made. The librarian reads the requirement, its plan, its gate decisions and its diff, then writes typed `doc` rows and LINKS them

• product-reviewer

  Use this agent when the user needs to verify that recent code changes satisfy all requirements from a plan document. Typical triggers include asking whether recent changes satisfy a phase or master plan's requirements, requesting a gap report between what was planned and what shipped, or asking for

• project-manager

  Use this agent when the guild needs to gather, refine, or document requirements. The project-manager interviews the user and creates the requirement document that the strategist plans from next. Spawned directly by the `new-requirement` skill for a live interview with the user (via relay), before th

• qa-strategist

  Use this agent when the guild needs a QA strategy: deciding what quality means for a product, mapping risk, and planning what to test. The qa-strategist surveys the running product and its specs, writes the risk map onto the board as `coverage` rows, builds an adversarial what-if input matrix, then

• qa-tester

  Use this agent when the guild needs to empirically test a running product: drive real scenarios, observe actual behavior, author end-to-end (Playwright) regression specs, and file reproducible bugs. The execution half of the guild's independent QA discipline. Authors e2e specs (devs co-maintain); co

• researcher

  Use this agent when the guild needs documentation research, API investigation, or technology evaluation. The researcher gathers information and writes findings into a reference document. Most often spawned directly and inline by the project-manager or strategist for a quick lookup; can also be dispa

• reviewer-architecture

  Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.

• reviewer-business-logic

  Use this agent for business logic code review. Verifies that acceptance criteria are met, business rules are correctly implemented, and the code is testable with proper unit test coverage. Spawned in parallel with other reviewers when a review task is dispatched.

• reviewer-edge-case

  Use this agent for edge case code review. Identifies unhandled boundary conditions, null/empty inputs, error scenarios, concurrency issues, and other robustness gaps. Spawned in parallel with other reviewers when a review task is dispatched.

• reviewer-security

  Use this agent for security-focused code review. Evaluates implementation against OWASP Top 10, checks for injection risks, authentication/authorization flaws, and sensitive data handling issues. Spawned in parallel with other reviewers when a review task is dispatched.

• strategist

  Use this agent when the guild needs architectural planning. The strategist reads requirements, analyzes the codebase, and produces an implementation plan with the developer/test-planner/reviewer tickets, and the requirement's execution graph — instantiated from a template and deviated from only with

• test-planner

  Use this agent when the guild needs a test plan after development completes. The test-planner inventories what was implemented, maps acceptance criteria to unit and integration test cases, composes the test plan, and creates the test-writer tickets that implement it. Spawned by the check-in skill wh

• test-writer

  Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a

Similar plugins