workaholic

Context detection and branch pattern matching for unified commands.

Use when the user runs `/catch`, asks to "catch me up", "what has everyone been working on", "summarize the last two weeks", or "show a by-developer development report". Scans the recent commit/ticket/story trail, fans out one collector per active developer to summarize their work, then synthesizes the overall development direction, the active missions (progress plus merged and unmerged in-flight work), and stands ready for follow-up questions.

Verify required plugin dependencies are installed.

Safe commit workflow with multi-contributor awareness and structured message format.

Use when the user runs `/ticket <description>` or asks to "write a ticket", "spec out a feature", or "draft an implementation plan". Discovers historical context, source code, and standards for the request, then writes an implementation ticket to `.workaholic/tickets/todo/` with frontmatter, key files, related history, implementation steps, and considerations.

The project's design (設計) engineering policies — how the product's interaction and experience are shaped, what data is handled with what access controls and sovereignty guarantees, how external dependencies are chosen, and what users and AI agents can reach without force. English hard copies of the canonical qmu.co.jp articles live in this skill's `policies/` directory; this index links to each. Preloaded as the policy lens wherever UX, security design, or API work is scoped or implemented.

Guidelines for discovering historical context, source code, and repository standards.

Use when the user runs `/drive` or `/implement`, asks to "implement the queued tickets", "work through the todo list", or "drive the backlog". Surveys the claimable missions and the unclaimed backlog, partitions them into PR-units, claims each unit on a pushed branch, implements it in the claim's own worktree, reports, and routes it by the unit's effective merge policy — identically in an interactive session and on the routine.

Answer a developer's question about the repository from verifiable evidence, render it as a printer-ready HTML report, and print it to PDF with a real browser (Playwright plugin or Chrome DevTools MCP), exporting to a given directory or the Desktop-then-Home default.

Use when a session needs to register a piece of feedback — a design conclusion, an instruction, a concern, or customer material — into the repository's feedback stream, or to list the accumulated stream. Feedback is the unified inbound record of project context; this skill defines its schema and owns its scripts.

Gather git context and ticket metadata in single calls.

The project's implementation (実装) engineering policies — how the code is structured so gaps in domain reasoning are machine-checkable early, the running system keeps serving and recovering, and information and function stay reachable through multiple paths including AI agents. English hard copies of the canonical qmu.co.jp articles live in this skill's `policies/` directory; this index links to each. Preloaded as the policy lens wherever code is scoped or implemented.

Use when the user runs `/mission`, asks to "start a mission", "plan a batch of work", "show mission progress", or "what missions are in flight". A mission is an optional, epic-equivalent grouping — a bounded, information-rich batch of two or more tickets an agent fleet drives together, never a required parent of any ticket; this skill creates one, lists missions with computed progress, and defines the mission schema every workflow reads.

Use when a session runs `/moderate` — the hourly maintenance tick that keeps the space around the loop judgeable. Defines the twenty-five-step run, the hourly thread it posts, what each step may write, the tick log it leaves behind, and the rulings the ask's steps are held to.

The runtime notification model — which events earn a Slack post, the exact post shapes, and the stateless reply-thread lookup — used by /implement's per-unit posts, /specificate's finish line and the description root it replies into, and the routine prompts, which defer to it.

Keep the project's .workaholic/ tree organized as an Open Knowledge Format (OKF) bundle - regenerate the bundle-root index.md and per-area indexes whenever a workflow writes knowledge documents.

The project's planning (企画) engineering policies — how projects are initiated with proper understanding of the business, market, and legal context before design and implementation begin. English hard copies of the canonical qmu.co.jp articles live in this skill's `policies/` directory; this index links to each. Preloaded as the policy lens wherever new features or projects are scoped.

Use when a session runs `/propose` or the `[Propose]` routine's clock fires — read the running identity's own active strategies, plan the one mission whose evolutionary move would bring the nearest one closer to its aim, and open that plan as a GitHub issue the next `/specificate` tick will ingest. Defines the mission grain, the eligibility gates, the three moves, the refusal of housekeeping, and the scripts.

Deterministic branch-safety scan used by /story (warn) and /ship (block) to catch credentials, oversized/too-many files, and unrelated client-work terminology leakage before a branch reaches a public remote.

Generate the branch story's review content (a Motivation past-context paragraph, Outcome, Concerns, Successful Development Patterns) from archived tickets and deferred concern verdicts. Used by the report workflow when assembling a PR story.

The project's safety (安全) policies — the company's information security commitments, privacy practices, and operational security standards, together with the procedures for reporting and responding to incidents and for managing risks under the ISMS framework. English hard copies of the canonical qmu.co.jp articles live in this skill's `policies/` directory; this index links to each. Referenced when setting up a new project, onboarding a collaborator, or handling a security incident.

Use when the user runs `/ship`, asks to "merge and deploy", "ship this branch", or "push to production". Pre-checks the workspace and todo queue, confirms with the user, merges the current branch's PR on GitHub, runs the deploy steps from CLAUDE.md's `## Deploy` section, and reports the outcome.

Use when a session has an ask in hand — the [Specificate] routine's clock tick that discovers one (the open GitHub issues assigned to this identity), or /specificate by hand — to judge it against the conservative bar and emit, in one publish-tree pull request, the feedback record together with whatever the judgment warrants. Defines the clock-fired discovery, the judgment bar, the four forms a proposal takes, the proposal schema, and the scripts.

Use when the user runs `/story` (or the deprecated `/story`), asks to "write up this branch", "open the PR", "create the release note", or "assess release readiness". Reads archived tickets, judges previously-deferred concerns, generates a branch story file, creates or updates the GitHub PR, writes the release note, and reports whether the branch is safe to ship.

Use when a session needs to record, list, read, or close a strategy — the operator's outbound, resolved direction, bounded by a schedule and carried by a named assignee. Defines the artifact's model and owns its scripts.

Prevent agents from modifying system-wide configuration in regular projects.

Validate that writer subagent output files exist and are non-empty before proceeding to index updates.

Gateway skill a repo's /workaholify setup refers to — reaches the engineering policies (the pillar policies/ directories) and states the working-directory ground rules, instead of duplicating rules into CLAUDE.md.

Release note content structure and guidelines for GitHub Releases.