gustavo-meilus/superpipelines / plugins/superpipelines/skills/sk-4d-method
sk-4d-method
VerifiedProvides a per-invocation four-phase processing wrapper (Deconstruct, Diagnose, Develop, Deliver) for structured request resolution. Use when an agent faces an ambiguous request, missing required slots, or feedback that requires re-entry into a specific processing phase.
4D Method — Per-Invocation Processing Wrapper
2. DIAGNOSE (Specs & Guardrails)
- Goal: Transform vague terms into concrete specifications.
- Replace subjective language (e.g., "clean," "professional") with measurable metrics (e.g., "≤80 chars/line," "no passive voice").
- Separate overloaded asks into a numbered sub-task list.
- Anticipate the top 2–3 failure modes and design build-time guardrails.
3. DEVELOP (Tactics & Strategy)
- Goal: Match the task type to the optimal execution strategy.
- Select the appropriate model tier and effort level per project model-resolution rules.
- Define output format precisely (schemas, bullet counts, code languages).
- Layer constraints using primacy and recency (critical rules first and last).
4. DELIVER (Formatting & Scannability)
- Goal: Ensure the response is optimized for the consumer's environment.
- Use an inverted pyramid structure (conclusion first).
- Match the medium (e.g., Slack-tight vs. report-structured).
- Provide an actionable next step.
4D Feedback Routing
<routing_table>
| Feedback Signal | Re-entry Phase | Rationale |
|---|---|---|
| "Not what I asked" | Deconstruct | Misaligned intent or goal. |
| "This is incorrect" | Diagnose | Technical failure or missed edge case. |
| "Use a different approach" | Develop | Correct intent, wrong implementation strategy. |
| "Format/style change" | Deliver | Cosmetic or presentation refinement. |
| </routing_table> |
Quick Reference
<quick_reference>
| Phase | Core Question | Key Action |
|---|---|---|
| Deconstruct | "What is actually being asked?" | Separate intent from output; surface gaps. |
| Diagnose | "Where will this break?" | Replace vague terms; resolve conflicts. |
| Develop | "What's the best approach?" | Match strategy to task; define format. |
| Deliver | "Is this ready for the consumer?" | Organize for scannability; match context. |
| </quick_reference> |
Cross-References
sk-pipeline-patterns/SKILL.md— Pattern 6 definition.sk-spec-driven-development/SKILL.md— SDD handoff rules.sk-claude-code-conventions/SKILL.md— Scaling and model selection.
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 |