Synthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Capture the decisions already made. Resolve only gaps that would materially change the intended behavior, scope, or feasibility; do not reopen settled questions for the sake of completing a template.
Inspect the relevant implementation, tests, domain language, and architectural decisions when they improve fidelity. Keep facts observed in the repository distinct from decisions inferred from the conversation.
Describe:
Prefer durable behavioral contracts over file paths and implementation recipes. Include code or a type shape only when it records a decision more precisely than prose.
Use the spec format when a structured document helps. Return, save, or publish the spec in the destination the user requested. Treat tracker publication and label changes as separate mutations requiring clear scope.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
The English summary is being prepared. Showing the original description.
Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.
The English summary is being prepared. Showing the original description.
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
The English summary is being prepared. Showing the original description.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
The English summary is being prepared. Showing the original description.
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
The English summary is being prepared. Showing the original description.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
The English summary is being prepared. Showing the original description.