mcpField
P
probe

probe

github.com/ilamanovDevelopment62 installs
Repository

About probe

Probe is a development skill for agreeing on the structure of a complex change before implementation. It creates real code stubs for key decisions, presents the alternatives, and stops once the user agrees.

Key features

  1. 01Identify decisions that shape the change
  2. 02Create stubs at their real file paths
  3. 03Use real types and signatures
  4. 04Explain decisions and difficult alternatives
  5. 05Stop without implementing after agreement

Use cases

  1. 01Agreeing on an API before implementation
  2. 02Reviewing schema and module boundaries
  3. 03Aligning on interfaces for a complex change

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ilamanov/skills --skill probe

After installing, type/probein Claude Code to confirm it loaded.

Details

From the project README

Probe

Goal

Agree with the user on the structure of a complex change before you implement it. Some decisions control all the other work, for example the schema, the API, the interfaces, and the module boundaries. If one of these decisions is wrong, much work must be done again. It is cheaper to agree on them first.

Steps

  1. Find the decisions that control the change. Only these decisions go into the skeleton.
  2. Write the stubs in real code. Put the files in their real locations. Use real types and signatures. Leave the bodies empty. Do not write logic or tests. Do not commit.
  3. Show the skeleton to the user. Give each decision in one line with the reason. If a decision was difficult, tell the alternative.
  4. Change the stubs until the user agrees. Do not add scope.

Rules

  • If the change is simple, tell the user that a probe is not necessary.
  • When the user agrees, stop. Do not implement the change.

Comments

Markdown supported