[Workflow] Implement a well-defined feature spec-first and test-first when its behavior is not yet captured in a canonical spec. Spec-complete behavior uses workflow-implement-spec.
The English summary is being prepared. Showing the original description.
[Documentation] Use when detecting codebase health issues: unused exports, doc count-drift, orphan files, stale config references.
The English summary is being prepared. Showing the original description.
[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
The English summary is being prepared. Showing the original description.
[Content] Use when a workflow step or the user asks for marketing strategy: positioning, channels, messaging, campaigns, budget and KPIs.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance and UX best practices.
The English summary is being prepared. Showing the original description.
[Workflow] Audit project architecture, scalability and production readiness without changing code; deliver one consolidated health report.
The English summary is being prepared. Showing the original description.
[Documentation] Use when a workflow step or the user asks for a refresh of every selected, evidence-applicable reference-doc scan target, or a --targets= subset, at once. One doc: scan; first-time setup: docs-manager --mode=init.
The English summary is being prepared. Showing the original description.
[Architecture] Use when a workflow step or the user asks for project architecture foundations, infrastructure and examples before feature implementation.
The English summary is being prepared. Showing the original description.
[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.
The English summary is being prepared. Showing the original description.
[Workflow] Research, design, specify and implement a large, ambiguous or research-heavy feature in an existing codebase.
The English summary is being prepared. Showing the original description.
[Architecture] Use when a workflow step or the user asks for tech-stack research: alternatives, trade-offs and user-validated recommendations.
The English summary is being prepared. Showing the original description.
[Testing] Use when a workflow step or the user asks for a local test run and read-only results summary.
The English summary is being prepared. Showing the original description.
[Documentation] Use when a workflow step or the user asks for canonical feature specs and test scenarios: author, audit, amend, tests and sync. discovery maps overlaps; clarify confirms decisions; index derives navigation/ERD.
The English summary is being prepared. Showing the original description.
[Workflow] Create or revise the canonical spec for one capability in the configured format, with reviewed cases and reconciled test evidence.
The English summary is being prepared. Showing the original description.
[Dev Data] Use when a workflow step or the user asks for idempotent QC happy-path seeders using public commands. --mode=review audits seeder conventions read-only.
The English summary is being prepared. Showing the original description.
[Utilities] Use when a workflow step or the user asks for an HTML session wrap-up: work, changes, rationale, how it works, stale docs and lessons.
The English summary is being prepared. Showing the original description.
[Git] Use when creating release notes or a release document from git history at any scope (tag, branch, time range), as markdown plus a standalone HTML presentation.
The English summary is being prepared. Showing the original description.
[Skill Management] Use when shared protocol checklists change and need propagating across skills.
The English summary is being prepared. Showing the original description.
[Research] Use when a workflow step or the user asks for web source discovery and triage into a source map and gaps. --chain=deep-dive also builds a cross-validated evidence base.
The English summary is being prepared. Showing the original description.
[Workflow] Investigate and fix bugs, crashes or regressions at the root cause, with reviewed changes and regression tests that prove the fix.
The English summary is being prepared. Showing the original description.
[Workflow] Use when E2E tests need to be written, updated or fixed: resolves the scope, authors tests only when needed, then verifies them through the configured runner in a bounded fix/retest loop.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when a workflow step or the user asks for rationale evaluation or critical judgment of a decision, claim or statement: necessity, options, trade-offs. --validate-findings checks findings; --fix-loop fixes. Diffs: changes-review.
The English summary is being prepared. Showing the original description.
[Utilities] Use when teaching Claude a lesson that persists across sessions, including an extra rule for one skill or task kind (routes to project-skill-protocol).
The English summary is being prepared. Showing the original description.
[Utilities] Use when a project adds, changes, lists or removes its OWN protocol rules layered over a framework skill (additive only). list | add | update | delete.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)