← ConsultorCONTENT HISTORY

Update to Consultor

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "resume-consultor",
  "description": "Resume an existing Consultor project by inspecting local consulting documents, initializing missing workspace structure, running the audit script, and asking the next highest-leverage question.",
  "included_files": [],
  "skill_md_contents": "---\nname: resume-consultor\ndescription: Resume an existing Consultor project by inspecting local consulting documents, initializing missing workspace structure, running the audit script, and asking the next highest-leverage question.\ncompatibility: Requires Python 3.11+ only when using the optional bundled workspace and audit helpers.\n---\n\n# Resume Consultor\n\nResume a Consultor project without restarting from scratch.\n\nDo not ask the user to repeat information that can be read from project files.\n\nAsk one question at a time after inspection.\n\n## First Actions\n\n1. Inspect for existing project state:\n   - `consultor/`\n   - `marketing/`\n   - `strategy/`\n   - `docs/`\n   - `brand/`\n   - `go-to-market/`\n   - `campaigns/`\n2. If `consultor/` does not exist, initialize the workspace:\n\n```bash\npython3 ../../scripts/consultor_init.py <project-root> --base-files --resume-note\n```\n\n3. If meaningful strategy or Consultor documents exist, run the audit:\n\n```bash\npython3 ../../scripts/consultor_audit.py <project-root> --stdout\n```\n\nResolve script paths relative to this `SKILL.md` file before running them.\n\n4. Use the audit to choose the next question.\n\n## Phase-Aware Resume\n\nRead `consultor/context.md` before asking the next question. If it contains a workshop phase, continue from that phase:\n\n- Interrogation: ask about the weakest missing core signal.\n- Contradictions: compare decisions, assumptions, risks, and evidence.\n- Synthesis: run audit and update summary documents.\n- Artifacts: create only the artifact needed for the current branch.\n- Validation plan: convert assumptions into experiments.\n- Resume: run init and audit before asking.\n\nIf no phase exists, infer the phase from the user's request and existing documents.\n\n## Question Selection\n\nPrioritize the missing or weakest item in this order:\n\n1. Exact audience.\n2. Problem, job, pain, or desire.\n3. Main alternative.\n4. Differentiation.\n5. Concrete offer.\n6. Proof or evidence.\n7. Channel or path to buyer/user.\n8. Next validation step.\n\n## Documentation\n\nWrite only real content:\n\n- Confirmed decisions.\n- Active assumptions or hypotheses.\n- Verified evidence.\n- Risks.\n- Open questions.\n- Next validation steps.\n\nDo not create decorative frameworks, empty files, or empty sections.\n"
}

SHA-256: 6b27c89aaae7228bda8002d9f49e393a3559f15f000a84c4989a47ad1b0e68b9