super-skilllisted

Apply the combined rigor + delegation framework for complex tasks. Two operating modes: (1) **Rigor mode** — use the GPT-5.6 Sol 7-step loop, 10 principles, 9-stage architecture, task classification, risk register, validation layers, acceptance/rejection criteria, adversarial review, and pre-delivery checklist (default for any non-trivial task); (2) **Delegation mode** — for codebase-heavy or token-heavy work that can be split into independent parallel slices, use the Efficient Fable delegation pattern: cheap subagents do the heavy lifting, the orchestrator keeps judgment, architecture, synthesis, and final review; always apply the vetting protocol (treat subagent reports as leads, not facts). Trigger when the user says "super skill", "use the super framework", "delegate this efficiently", or any complex task where you want both auditable artifacts AND cost/speed efficiency. Do NOT trigger for trivial single-step questions, or for tasks that don't tolerate any subagent delegation (legal, medical, single-sourc
anshmajumdar121/skill-x · ★ 0 · AI & Automation · score 72

Install: claude install-skill anshmajumdar121/skill-x

# Changelog (self-evolution audit trail) | Date | Change | Reason | Evidence | Reversible? | |---|---|---|---|---| | 2026-07-17 | Initial synthesis of TLG + efficient-fable | First version | Both parent SKILL.md files | Yes (git) | | 2026-07-17 | Added Self-Evolution Protocol (this section + `references/self-evolution.md`) | User requested automatic improvement capability with strict internal guardrails | User request; standard skill-evolution pattern | Yes (changelog) | # SuperSkill (Rigor + Delegation) Two-mode skill combining the **rigor** of the GPT-5.6 Sol execution framework with the **delegation efficiency** of the Efficient Fable pattern. The rigor mode is the default outer loop; delegation mode is opted into when the task is parallelizable and token/codebase-heavy. > Parent skills: `think-like-gpt-5-6` (rigor framework), > `efficient-fable` (delegation pattern). This skill is a synthesis — > both parent skills remain installed for their own direct triggers. Use > this skill when you want both at once. ## Inputs to collect In all cases, the intake record from `references/principles-and-loop.md` §3. Plus a **delegation eligibility check** (NEW for SuperSkill): - **Is the work parallelizable?** Can the task be sliced into chunks that don't depend on each other? If yes → consider delegation mode. - **Where is the expensive-token risk?** Large repo search, long logs, broad docs, repetitive edits, or heavy generation? - **Is there a cheaper subagent available?**