Menu
Which user-only agent workflow to run — grilling, docs-aware grilling, teaching, or meta authoring help.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | ask-agents |
| description | Which user-only agent workflow to run — grilling, docs-aware grilling, teaching, or meta authoring help. |
| disable-model-invocation | true |
Zero context load — you pick the workflow.
/grill-with-docs — sharpen the idea; inline updates to docs/ (architecture / roadmap / glossary / plans) as decisions land. No codebase yet? Use /grill-me (standalone below).docs/plans/<name>.md → split into GitHub issues. Fresh session per issue.tdd + workflow skills appropriate to this repo in the same window./harden-pr — lite after each tracer slice; full before PR ready.Keep grilling + plan authoring in one window until issues are filed. Each implement session starts fresh from the plan/issue. If the window nears the smart zone, write a compact plan in docs/plans/.
/improve-codebase-architecture — surface deepening opportunities; pick one → back to main flow at grill-with-docs./diagnosing-bugs — hard bugs and perf regressions (model-invoked skill — not a router target)./docs-lifecycle-sweep on docs/ (model-invoked)./compact — built-in: same session, summarized history — use only at phase breaks.docs/plans/<name>.md or the GitHub issue.| Invoke | When |
|---|---|
grill-me | Sharpen a plan with no codebase (stateless) |
writing-great-skills | Skill vocabulary + principles |
writing-agents-config | Codemap repo tier/pairing deltas |
domain-modeling | Ubiquitous language inline + batch glossary |
tdd | RED→GREEN tracer-bullet TDD |
verify-after-each-step | Per-file checks after each milestone |
diagnosing-bugs | Debug loop for hard bugs |
teach | Multi-session learning workspace (missions, lessons, retrieval practice) |
Meta: agents-tier-system.
Voice, tone, and format for the public Codemap docs (`apps/docs`, built with Blume). Use when authoring or editing apps/docs prose — landing, guides, concepts, recipes, reference, generated API — or deciding headline grammar, benefit framing, peer framing, or anti-pitch wording.
Repo-wide docs framework — what `docs/`, `docs/plans/`, `docs/research/`, `.agents/`, or any other doc-bearing surface in this repo looks like, what lifecycle each doc follows, and how to keep cross-references intact when slimming or moving content. Use when authoring or editing any `docs/**`, `docs/plans/**`, `docs/research/**`, `.agents/rules/**`, `.agents/skills/**`, or any new doc-bearing folder. Defines the lifecycle types (Reference / Roadmap / Plan / Audit / Research), the existence test every doc must pass, the closing-state lifecycles (delete + lift; never "Slim & keep in plans/"), the substrate variants (single `audit.md` vs `audits/<topic>.md`; conditional `glossary.md`), the surface tiers (repo-wide / per-tooling-area), and the cross-reference preservation discipline (grep before slim; preserve rule numbers cited from source). The Tier-2 priming layer at `.agents/rules/docs-governance.md` cites this skill and extends with codemap-specific bits only.
Bring a branch to pristine, maximum production readiness without changing PR intent — spawn parallel Task subagents (never inline review), fix in-bounds findings, loop autonomously until clean or pass cap, then report once. Use after a tracer-bullet commit (lite), before PR is done (full), on "harden", "harden-pr", "pristine", "review until clean", "production-ready pass", or "harden-pr reconcile". Invoking this skill authorizes one harden commit at cycle end. NEVER stop mid-loop to ask about commits, babysit, or the next pass. NEVER redesign the feature or change observable runtime behavior.
The product north-star — four Codemap tenets (structural over semantic, predicate-as-API, local-first / agent-native surfaces, honest scope). Use when making a design, API, or architecture decision, evaluating a trade-off, justifying a feature, or writing/reviewing a docs/plans entry.
Keep apps/docs in sync with merged product changes. On each run, audit recently merged PRs against docs content, update only drifted pages, regenerate API MDX when public exports/JSDoc drifted, verify with blume validate/check/build/audit, and open or update a docs/* PR — or report a clean no-op.
Delta-driven dependency upgrades — a script gathers the evidence, you read the artifact and judge. Use when the user asks to upgrade, bump, or CVE-audit dependencies.