Find The Most Meaningful Entanglement
openbooklet.com/s/find-the-most-meaningful-entanglementopenbooklet.com/s/find-the-most-meaningful-entanglement@1.0.0GET /api/v1/skills/find-the-most-meaningful-entanglementCreate a small, high-quality set of new Beads (âbrâ issues) for a repo based on quick repo understanding + a user-specified focus.
Create an ExecPlan (execution plan) from a PRD, RFC, voice note, or brainstorming blurb, following the repo's PLANS.md. Use when the user asks for an exec plan, execution plan, or ExecPlan, or wants a PRD/RFC turned into a step-by-step plan.
Reads an existing ExecPlan, deeply analyzes every referenced file and code path in the codebase, then rewrites the plan with concrete, code-grounded improvements. Use when user asks to improve an execplan, review a plan, make a plan better, audit an execplan, refine a plan, strengthen a plan, or says "improve the plan."
Explore the codebase and identify **one** real bug most likely to cause user-visible harm: wrong outputs, lost data, silent failures, corrupted state, or incorrect logic. Style issues and hypothetical risks don't count.
Execute a pending execution plan from the .agent folder. Use when user asks to implement an execplan, execute the plan, run the pending plan, or mentions execplan-pending.md.
Suggest one consolidation refactor that reduces surface area (fewer concepts, fewer files) after deep repo analysis. Use when the user asks to simplify architecture, consolidate modules, reduce conceptual surface area, merge similar subsystems, or produce an ExecPlan for a chosen simplification.
Update ARCHITECTURE.md after implementing an execution plan. Use when user asks to update architecture docs, sync architecture, refresh architecture after implementation, or mentions updating docs post-execplan.
Auto-indexed from grp06/useful-codex-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.