mdnm/kaabalah-lightning-path

Overview

This skill uses the Kaabalah Lightning Path (Kether→Malkuth) to turn vague ideas into concrete, executable plans. It structures scope, architecture, success criteria, risks, dependencies, and a launch outcome so you can move from intent to delivery quickly. The result is a compact plan and a follow-up artifact ready for execution.

How this skill works

The skill prompts you to capture each node of the Lightning Path in short bullets, then highlights and confirms the critical nodes: Kether (what/why), Binah (components/definition of done), Geburah (risks/legal), and Yesod (QA/success metrics). It produces a recommended output with standardized headings (kether, chokhmah, binah, daath, chesed, geburah, tipharet, netzach, hod, yesod, malkuth). Finally, it helps create a deliverable artifact (doc, pitch, or prototype) and next-step execution tasks.

When to use it

• You have a fuzzy but important idea and need a clear path to execution.
• Planning a new product feature, pilot, or research project with uncertain scope.
• Preparing a concise artifact (pitch, brief, or prototype) for stakeholders.
• Defining launch criteria, QA, and dependencies before committing resources.
• Translating strategic intent into concrete tasks and owner responsibilities.

Best practices

• Keep each node to 1–5 bullets; focus on clarity and actionable detail.
• Confirm the four critical nodes early: what/why, components/DOD, risks, success metrics.
• Avoid premature announcements — record timing and escalation rules under netzach.
• List dependencies explicitly (people, tools, contracts) and map owners.
• Produce a single daath artifact (document, pitch, prototype) before execution.

Example use cases

• Drafting a one-page execution plan for a new product feature with clear DOD and QA metrics.
• Converting high-level research goals into a concrete experiment plan with risks and dependencies.
• Preparing a launch checklist and stakeholder pitch that lists legal/compliance constraints.
• Defining learning objectives and assessment criteria for a training module.
• Mapping vendor and contract dependencies before scheduling a pilot deployment.