agentsclimarketplace

Interview

Skill DavisMcCracken/pyxis/skills/interview

Installable Python agent workflow: AGENTS.md rules plus skills for scaffold, TDD, debugging, refactoring, and handoff.

Install
npx -y skills add DavisMcCracken/pyxis --skill interview

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interview the user relentlessly about a plan or design, resolving each branch of the decision tree until you reach shared understanding. Use when the user wants to stress-test a plan, get grilled on a design, or says "interview" or "grill me".

SKILL.md

2.2 KB, as published. Nobody here has run it

Interview

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Docs layer (conditional)

Run the behaviours below only when the project already keeps domain docs (CONTEXT.md/CONTEXT-MAP.md at root, or docs/adr/) or the user asks to record decisions. Otherwise it's a plain interview — never seed doc conventions into a repo that hasn't opted in.

  • Glossary conflicts — user's term contradicts CONTEXT.md? Call it immediately: "Glossary says 'cancellation' means X; you seem to mean Y — which?"
  • Fuzzy terms — vague or overloaded word? Propose the canonical one: "'account' — Customer or User? They're different things here."
  • Concrete scenarios — when domain relationships come up, invent edge-case scenarios that force precise boundaries between concepts.
  • Code as witness — user claims a behaviour? Check whether the code agrees; surface contradictions: "Code cancels whole Orders, but you said partial cancellation exists — which is right?"
  • Inline CONTEXT.md updates — a term resolves → write it immediately, never batch. Format: ../_shared/CONTEXT-FORMAT.md. Domain-expert terms only; no implementation details.
  • ADRs, sparingly — offer only past the three-part gate (hard to reverse + surprising without context + real trade-off). Gate and format: ../_shared/ADR-FORMAT.md.

Handoffs

  • Design settled, single-session build → tdd.
  • Design settled, multi-session build → to-prd.
  • Plan turns out to hinge on an architectural problem → refactor.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.