hirokata
01Plugin Claude Code
A curated collection of Claude Code plugins for enhanced development workflows.
Plugin Claude Code
A curated collection of Claude Code plugins for enhanced development workflows.
Plugin Claude Code
Continuous agent orchestration system. A live 3-way interview between product-owner, architect, and user plans each requirement up front; the board then drives parallel development, test planning, unit & integration testing, and a 4-reviewer pass that produces a report for user-approved fixes, with a Svelte/SvelteKit…
Agent
Use this agent when the guild needs architectural planning. The architect reads requirements, analyzes the codebase, and produces implementation plans with specific developer tasks. Spawned directly by the new-requirement skill, alongside the product-owner — not spawned via a board ticket.
Agent
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 an implementation…
Agent
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.
Agent
Use this agent when the guild needs to gather, refine, or document requirements. The product-owner interviews the user, creates requirement documents, and collaborates with the architect. Spawned directly by the new-requirement skill for a live interview with the user (via relay) and, when in scope, the architect …
Agent
Use this agent when you need to verify that recent code changes satisfy all requirements from a plan document. Examples: Context: User has completed implementing features from a phase plan user: "Review if my recent changes satisfy all the requirements in the phase 3 plan" assistant: "I'll use the Task tool to launch…
Agent
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 strategist surveys the running product and its specs, builds a coverage matrix and an adversarial what-if input matrix, then declares qa-tester missions. It is the planning half of…
Agent
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); covers e2e against…
Agent
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 product-owner or architect for a quick lookup; can also be dispatched by check-in…
Agent
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.
Agent
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.
Agent
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.
Agent
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.
Agent
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, writes the test plan as a plan slice, and declares the test-writer tickets that implement it. Spawned by the check-in skill when a…
Agent
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 test-writing task…
Skill Claude CodeCodex
This skill should be used when the user says "check in", "clock in", "standup", "guild check in", "what's the status", "let's get to work", "start 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 as the guild…
Skill Claude CodeCodex
This skill should be used when the user asks to "clear the board", "reset the guild", "start fresh", "wipe the board", "clear all tasks", "reset the board", or wants to remove all current work from the guild board and start over.
Skill Claude CodeCodex
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 audit", "quality…
Skill Claude CodeCodex
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, Node.js scripts…
Skill Claude CodeCodex
This skill should be used when the user says "discuss", "let's discuss", "discuss [topic]", "talk about", "let's talk about", "summarize the context", "what are we working on", "break down the topics", "what subjects do we have", "let's review the context", "recap the conversation", or any phrase asking to analyze and…
Skill Claude CodeCodex
This skill should be used when the user asks for "guild status", "board status", "show the board", "what's on the board", "project status", "show guild", "guild board", or "what's happening". Shows a quick read-only view of the guild board without starting the work cycle.
Skill Claude CodeCodex
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 3-way interview between the product-owner, the architect, and the…
Skill Claude CodeCodex
Pre-loaded QA artifact formats for the qa-strategist and qa-tester agents. Defines the evergreen .guild/qa/ files — charter (quality definition, risk map, coverage matrix, oracle ledger), missions (scope, what-if input matrix, oracle sources), the bug ledger, session logs, and the regression manifest that points at…