Run any Skill in Manus with one click

grill-me-mateo

Stars8

Forks0

UpdatedMay 7, 2026 at 09:48

Grill me on a plan or change before I write code, but with my canonical four questions baked in — package boundary, error code, vertical slice, ADR. Use when the user says "grill me", "stress-test this", or before starting a non-trivial feature in ait, mateonunez.co, or any repo set up via setup-mateonunez-skills.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mateonunez

mateonunez/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	grill-me-mateo
description	Grill me on a plan or change before I write code, but with my canonical four questions baked in — package boundary, error code, vertical slice, ADR. Use when the user says "grill me", "stress-test this", or before starting a non-trivial feature in ait, mateonunez.co, or any repo set up via setup-mateonunez-skills.

Grill me (Mateo edition)

Interview me about the change relentlessly until every branch of the design tree is resolved. Ask one question at a time. Don't accept hand-wave answers — re-grill until the answer is concrete.

Always cover these four before letting me start:

Package boundary. Which workspace package owns this? If "shared", what's the third caller justifying it? See vertical-slices.
Error code. What can fail, and what code does each failure get on the AItError (or domain equivalent)? See result-not-throw.
Vertical slice. Is this a new slice or a deepening of an existing one? If new, name the package; if deepening, name the file.
ADR. Does this decision need an ADR in docs/adr/? If the answer is "maybe", it's a yes — write the ADR before the code.

Then carry on with the rest of the grilling — data shape, test seam, boundary code, deployment surface, rollback. Don't stop until I'm bored of answering.

More from this repository

same repository

code-review

mateonunez/skills

Review a diff or PR against my conventions — Result not throw, vertical slices, AItError codes, node:test, Biome, entity normalisation, a11y. Findings are triaged by severity (correctness → conventions → polish), not piled in a flat list. Use when reviewing a diff, reviewing a PR before merge, self-reviewing before opening a PR, or when user says "review this", "review the diff", "code review", or invokes `/code-review`.

2026-05-128

caveman

mateonunez/skills

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.

2026-05-078

to-issues

mateonunez/skills

Break a plan, spec, or PRD into independently-grabbable issues using vertical-slice tracer bullets. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

2026-05-078

to-prd

mateonunez/skills

Turn the current conversation context into a PRD and publish it to the issue tracker. Use when user wants to create a PRD from the current context.

2026-05-078

triage

mateonunez/skills

Triage issues through a state machine driven by triage roles. Use when you want to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

2026-05-078

write-a-skill

mateonunez/skills

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

2026-05-078

name	grill-me-mateo
description	Grill me on a plan or change before I write code, but with my canonical four questions baked in — package boundary, error code, vertical slice, ADR. Use when the user says "grill me", "stress-test this", or before starting a non-trivial feature in ait, mateonunez.co, or any repo set up via setup-mateonunez-skills.

Grill me (Mateo edition)

Interview me about the change relentlessly until every branch of the design tree is resolved. Ask one question at a time. Don't accept hand-wave answers — re-grill until the answer is concrete.

Always cover these four before letting me start:

Package boundary. Which workspace package owns this? If "shared", what's the third caller justifying it? See vertical-slices.
Error code. What can fail, and what code does each failure get on the AItError (or domain equivalent)? See result-not-throw.
Vertical slice. Is this a new slice or a deepening of an existing one? If new, name the package; if deepening, name the file.
ADR. Does this decision need an ADR in docs/adr/? If the answer is "maybe", it's a yes — write the ADR before the code.

Then carry on with the rest of the grilling — data shape, test seam, boundary code, deployment surface, rollback. Don't stop until I'm bored of answering.