From lz-advisor
This skill should be used when the user wants to implement, build, or execute a coding task with strategic advisor guidance. Trigger phrases include "implement this task", "execute this plan", "build this feature", "code this up", "lz-advisor.execute", "start building", "implement with guidance", "build this with advisor help", "execute the plan", and "code this feature". This skill pairs Sonnet execution with Opus strategic consultation for near-Opus intelligence at Sonnet cost. It follows a six-phase workflow: orient, consult, execute, make durable, final review, and complete. Optionally accepts a plan file from lz-advisor.plan via @ file mention. This skill should NOT be used when the user wants to plan before coding, review completed code, or run security audits -- those are handled by sibling skills lz-advisor.plan, lz-advisor.review, and lz-advisor.security-review respectively.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lz-advisor:lz-advisor.executeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The lz-advisor:advisor agent is backed by a stronger model (Opus). Invoke it
The lz-advisor:advisor agent is backed by a stronger model (Opus). Invoke it via the Agent tool at the strategic moments described below. For detailed guidance on timing, advice weight, and context packaging, see:
@${CLAUDE_PLUGIN_ROOT}/references/advisor-timing.md
@${CLAUDE_PLUGIN_ROOT}/references/context-packaging.md
This skill follows a six-phase workflow: orient, consult before work, execute with conditional advisor calls, make deliverable durable, consult before done, then complete.
## Phase 1: OrientUnderstand the task scope and current codebase state before doing any work.
If the user mentioned a plan file (via @ file reference), read it first. Use the plan's Strategic Direction and Steps as the foundation for the task. Orient by verifying the plan's assumptions against the current codebase -- check that referenced files exist, patterns match, and dependencies hold. Skip redundant exploration the plan already covers.
If no plan file was mentioned, orient from scratch:
node_modules/*/dist/.Do not write code or make changes during orientation. Do not consult the advisor yet -- orientation is preparation, not substantive work.
## Phase 2: Consult the AdvisorBefore starting substantive work, invoke the lz-advisor:advisor agent via
the Agent tool. Package the pre-execute consultation prompt per the
Proposal template in
@${CLAUDE_PLUGIN_ROOT}/references/context-packaging.md.
Carry out the task following the advisor's strategic direction. Read files, write code, run tests, iterate on errors. This is the substantive work phase.
Give the advisor's guidance serious weight. If a step fails empirically, or primary-source evidence contradicts a specific claim, adapt. A passing self-test is not evidence the advice is wrong -- it is evidence the test may not check what the advice checks.
During execution, consult the advisor again when:
Do not re-consult for:
Keep re-consultation prompts brief (2-3 sentences): what changed, what options are being considered, what decision is needed. These calls reuse the pre-execute consultation context implicitly; a full orient repackage is unnecessary.
If findings point one way and the advisor points another, do not silently switch. Surface the conflict in one more advisor call: "I found X, you suggested Y -- which constraint breaks the tie?" The advisor saw the evidence provided but may have underweighted it; a reconciliation call is cheaper than committing to the wrong branch.
Use the Proposal (short form) variant in
@${CLAUDE_PLUGIN_ROOT}/references/context-packaging.md. Two to three
sentences covering what changed, what options are being considered, and
what decision is needed. The pre-execute consultation context carries
implicitly; a full repackage is unnecessary.
Before the final advisor consultation, make the deliverable durable.
git add . or
git add -A) and create a commit with a clear messageThe commit ensures work survives if the session ends during the final advisor call. An unwritten or uncommitted result does not persist.
## Phase 5: Final Advisor ConsultationAfter committing, invoke the lz-advisor:advisor agent one more time.
Package the final review consultation prompt per the Verification template
in @${CLAUDE_PLUGIN_ROOT}/references/context-packaging.md. Include a
summary of changes made, test results if applicable, and the commit
reference.
This is a final check, not a request for approval. The advisor verifies the approach is sound and flags concerns the executor may have missed.
## Phase 6: CompleteIf the advisor flagged concerns in the final consultation:
If the advisor confirmed the approach is sound, present the completed work to the user: summarize what was built, what files were created or changed, and what tests pass.
After completing the task, present a summary to the user. If the work was informed by a plan file, note any deviations from the original plan.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub layzeedk/lz-advisor-claude-plugins --plugin lz-advisor