cogni-consult

Regenerate the cogni-consult engagement dashboard HTML from current engagement state without user interaction.

Map ONE cogni-consult stakeholder persona's empathize-stage empathy map (thinks/feels/says/does), extract their needs, and return a structured empathy-map envelope. Read-only — never edits the persona files, the artifact, or any state.

Score a finished cogni-consult deliverable against its stored chosen_framework and report structural drift as concrete, actionable findings. Read-only — never edits the artifact or any state file.

Challenge a cogni-consult deliverable as ONE acting stakeholder persona, in that persona's voice, and return a structured objection envelope. Read-only — never edits the artifact, persona files, or any state.

This skill should be used when the user wants to manage the WBS of a cogni-consult engagement — listing each action field's deliverables and their status, planning a field's deliverable set, picking the next deliverable to work, adding/splitting/merging action fields after scoping, or setting a deliverable's schedule (due date, effort, owner, milestone). Trigger on: "show the WBS", "action fields dashboard", "what deliverables are open", "plan the deliverables", "next deliverable", "add an action field", "split this field", "merge two action fields", "set a deliverable's due date", "set the start date/effort/owner", "mark a deliverable as a milestone", "schedule the deliverables", or when consult-scope hands off a freshly scoped engagement. Double Diamond phase phrasing ("discover phase", "deliver phase status") refers to a legacy engagement model no longer in the ecosystem; new consulting work lives in cogni-consult (this skill owns its WBS and deliverable management).

Generate an interactive HTML dashboard showing a cogni-consult engagement's status — action fields, deliverables, design-thinking stage, and persona-review progress. Use whenever the user mentions dashboard, engagement dashboard, engagement status, "show me the engagement", "visualize the engagement", WBS view, status overview, or wants to see the engagement in a browser — even if they don't say "dashboard".

This skill should be used when the user wants to produce a deliverable of a cogni-consult engagement by running its design-thinking loop — empathize→define→ideate→prototype→test on one deliverable inside an action field. Trigger on: "work the deliverable", "run design thinking on <deliverable>", "produce the <deliverable> deliverable", "start the DT loop", "draft the deliverable", "continue the deliverable", or when a WBS dashboard recommendation hands off the next unstarted deliverable. Starting a fresh (not-yet-in-progress) deliverable requires a satisfied personas gate: when it is unsatisfied the loop routes to consult-personas first before opening, so a fresh start may bounce to persona seeding or a waiver. Global phase phrasing ("discover phase", "develop phase", "diamond") refers to a legacy engagement model no longer in the ecosystem — do not run this loop against legacy engagement directories; cogni-consult has no engagement-level phases; design thinking runs per deliverable.

This skill should be used when the user wants to manage or invoke the acting stakeholder personas of a cogni-consult engagement — defining personas from the scope's Stakeholder dimension, enriching one with evidence, or having a persona challenge a deliverable in its own voice. Trigger on: "set up the personas", "add a stakeholder persona", "enrich the persona", "challenge this deliverable as the partner", "act as the project manager", "persona review", "what would the partner say", or when a design-thinking test stage requests a persona challenge. Design-for persona phrasing tied to Double Diamond phases ("discover personas", "persona for the define phase") belongs to a legacy engagement model no longer in the ecosystem — cogni-consult personas act and challenge, they are not phase artifacts.

This skill should be used when the user wants a phased roadmap or timeline of a cogni-consult engagement's own WBS deliverables — sequenced from the dependency graph and durations and written as an Obsidian-browsable markdown artifact. Trigger on: "project plan", "engagement timeline", "roadmap", "show the roadmap", "gantt", "gantt chart", "schedule the engagement", "when does the engagement finish", "plan the timeline", "render the project plan", or when a WBS/dashboard view hands off a request for the sequenced plan — even if the user doesn't say "project plan" explicitly. This is an INTERNAL engagement-management view (a read-mostly sibling of consult-dashboard and consult-resume), not a client-facing content producer. Double Diamond phase phrasing ("discover phase", "deliver phase timeline") refers to a legacy engagement model no longer in the ecosystem; cogni-consult engagements have no phases — the roadmap phases here are the derived topological layers of the deliverable graph, not engagement stages.

Executive-advisory voice — answer-first, hypothesis-driven, structured options