tzachbon/smart-ralph / plugins/ralph-specum/skills/interview-framework
interview-framework
VerifiedThis skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.7 KB |
| references/algorithm.md | markdown | 6.1 KB |
| references/domain-modeling.md | markdown | 2.1 KB |
| references/examples.md | markdown | 2.8 KB |
references/examples.md
View on GitHub# Grilling Examples
## Whole critical frontier
Suppose requirements has three independent critical decisions: primary user, compatibility promise, and data retention. Ask all three in one `AskUserQuestion` call. Put `[Recommended]` on the grounded first option for each and name its tradeoff. Do not ask repository framework, output path, or ticket number when those facts are discoverable.
If five independent critical decisions are open, ask four in the first call and one in the second. The tool maximum is the only batching reason.
Resolve repository facts and domain language before asking. For example, inspect the active authentication boundary and its `CONTEXT.md` definition instead of asking which module owns it. Ask only when the remaining boundary choice materially changes the artifact.
## Partial answer
The user answers the primary-user and retention questions but omits compatibility.
1. Record both answered decision IDs immediately.
2. Leave compatibility open.
3. Recompute dependencies.
4. Ask compatibility plus any decisions it unblocked.
Do not discard the two saved answers or restart the round.
If the user selects `Other`, create a specific dependent decision from the supplied alternative. Do not ask a generic "what did you have in mind?" question.
## Control-only reply
Active frontier: architecture boundary and rollout safety.
User: `proceed`
Result: persist no answer, keep both decisions open, and ask the same frontier again. `continue`, `go ahead`, and `apply the changes` behave the same way.
## Bare skip
Active frontier: test depth and rollback policy.
User: `skip`
Result: record the phase interview as skipped with the recommended test depth and rollback policy listed as defaults and assumptions. Present those choices in the final decision brief and require explicit approval before delegation.
User: `Skip browser tests; keep the rollback task.`
Result: treat the reply as substantive. Persist both decisions. It is not a bare skip.
## Final approval
Present:
```text
Decision brief
- Scope: existing API only
- Compatibility: preserve the current client contract
- Approach: extend the current module
- Tradeoff: smallest change, but keeps the current coupling
- Assumptions: current deployment pipeline remains available
```
Ask `Approve and delegate`, `Revise decisions`, or `Cancel`. Only the explicit approval selection completes the gate. After approval, call the helper check and launch the artifact agent in the same response.
## Artifact revision
After the agent writes `design.md`, the user says `apply the changes` and supplies reviewer findings.
Result: delegate the revision with those findings, show the updated walkthrough, and ask for artifact approval again. Keep the phase in artifact approval until the user explicitly approves.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |