grill-me
Run a rigorous decision-clarification loop for the user's plan or design.
Use this loop:
- Identify open decisions, assumptions, dependencies, and risks.
- Prioritize the single highest-leverage unresolved decision (the one most likely to unblock other choices or prevent rework).
- Ask one focused question that resolves that decision.
- Summarize current understanding, including what is now decided, what remains open, and why the next question matters.
- Repeat until exit criteria are met.
Choose evidence source before asking:
- Inspect available artifacts (codebase, docs, specs, prior decisions) first when the answer is factual and recoverable from existing information.
- Ask the user directly when the answer is preference-, strategy-, risk-tolerance-, or business-priority-dependent.
Separate elicitation from recommendation:
- During elicitation, avoid leading phrasing and avoid presenting a preferred answer in the question.
- After enough context is collected for a decision, provide a recommendation with rationale, tradeoffs, and explicit assumptions.
More from blogic-cz/blogic-marketplace
marketing-expert
This skill should be used when writing or rewriting marketing copy for software products, including positioning, messaging, homepage rewrite work, landing pages, product descriptions, conversion-focused updates, and sales-enablement content. Produces clear, truthful, high-performing SaaS copy.
97requirements
This skill should be used when clarifying a feature, writing a requirements spec, running a structured discovery session, or when users mention requirements-start, requirements-status, requirements-current, requirements-list, requirements-remind, or requirements-end.
78frontend-design
This skill should be used when a task requires designing or implementing frontend UI (components, pages, layouts, styling) and no more specialized frontend skill is a better fit. It guides production-grade, brand-consistent visual implementation with distinctive but controlled aesthetics.
78testing-patterns
This skill should be used when implementing or reviewing testing workflows in template-ts projects, especially for testing, Vitest, Playwright, integration test, and mocking scenarios.
76git-workflow
Automates the full PR lifecycle — create or update a pull request, then aggressively monitor CI checks and review feedback in a continuous loop, fixing failures and addressing comments until the PR is fully green. Also covers push, branch creation, and branch sync workflows.
76debugging-with-opensrc
Load this skill when debugging behavior in external libraries by reading local OpenSrc mirrors (Effect, TanStack, TRPC, Drizzle, Better Auth, Sentry, Pino), or when docs conflict with runtime behavior and source-level verification is required.
75