probe-understanding-manager

Probes user understanding of engineering designs through manager-style questioning and scored markdown reports.

3|Updated Feb 15, 2025
One-click install
npx skills add https://github.com/mark-torres10/ai_tools --skill probe-understanding-manager-mark-torres10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probe-understanding-manager
Source: https://github.com/mark-torres10/ai_tools/tree/main/skills/probe-understanding-manager
Command: npx skills add https://github.com/mark-torres10/ai_tools --skill probe-understanding-manager-mark-torres10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineers often believe they understand a design or plan until someone challenges it. This Skill pressure-tests your grasp of a feature, migration, or architecture by simulating a demanding engineering manager who asks one probing question at a time and exposes gaps in requirements, trade-offs, and operational readiness. ## Core Features & Use Cases - Multi-Round Probing Loop: Runs an adaptive questioning session covering problem framing, functional and non-functional requirements, assumptions, architecture trade-offs, and rollout risks. - Critical Feedback After Each Answer: Evaluates clarity, correctness, precision, and missing assumptions, then adapts the next question to the weakest area. - Scored Markdown Report: Writes a structured report with a 10-category rubric (comprehension, correctness, precision, depth, reasoning, and more) to probe_understanding/<timestamp>_<topic>/main.md. - Use Case: Before a design review, rehearse explaining your database migration plan and receive a scorecard showing that your rollback strategy and failure-mode analysis need work. ## Quick Start Ask the assistant to act as your engineering manager and pressure-test your design or implementation plan, then answer its questions one at a time.

Frequently Asked Questions about probe-understanding-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I practice explaining a system design before a review?

Start a probing session by describing your design in your own words. The skill asks one question at a time about requirements, trade-offs, and failure modes, then delivers a scored report highlighting your weakest areas.

How does engineering manager style feedback work in this skill?

After each answer you receive one to three sentences of critique naming what was vague or missing, followed by a follow-up question targeting the weakest area. The stance is constructive but deliberately demanding.

What topics can be pressure-tested with this skill?

Any engineering work at any stage: feature designs, migrations, architecture decisions, implementation plans, rollouts, and postmortems. It probes functional and non-functional requirements, assumptions, trade-offs, and operational readiness.

What output does a probing session produce?

A markdown report saved to probe_understanding/<timestamp>_<topic>/main.md containing a summary, ten rubric scores out of 10, strongest areas, gaps and critique, a stronger version of your answer, and practice questions.

When should I not use a manager-style probing session?

Avoid it when you need direct implementation help, code generation, or quick factual answers. The skill only asks questions and critiques your reasoning; it does not design or build the system for you.