business-context-os: Skill for Claude Code

Clear Planner

Purpose

Creates implementation plans. Invoked FIRST for every user request.

This skill IS:

• The mandatory entry point for the PLAN phase of any significant work
• An 8-step workflow that produces approved implementation plans
• The bridge between user intent and structured execution

This skill IS NOT: Executing the plan (that's the builder's job)

---

8-Step Workflow

Step 1: Understand Intent        -> Create planning-manifest.json
    |
Step 2: Run Discovery
    |
Step 3: Detect Scenario (agenting / documentation)
    |
Step 4: Gather Context           <- Return here on "Adjust" or "Modify"
    |
Step 5: Load Scenario Template
    |
Step 6: Present Approach         -> GATE: "Proceed" / "Adjust"
    |
Step 7: Create Session Artifacts -> Creates plan-manifest.json + implementation-plan.md
    |
Step 8: Present Full Plan        -> GATE: "Approve" / "Modify" / "Cancel"
    |
HANDOFF to implementation

Self-tracking: See references/planning-workflow-schema.md for the planner's own state tracking.

---

Step 1: Understand Intent

Parse the user's request:

• What do they want to accomplish?
• What files/systems are involved?
• Is there a clear objective?

Create the session folder + planning-manifest.json in one step:

.claude/quality/sessions/{YYYYMMDD}_{HHMMSS}_{slug}/
  planning-manifest.json   <- Track planner's own workflow state

Do NOT call mkdir first. Use the Write tool directly on .claude/quality/sessions/{YYYYMMDD}_{HHMMSS}_{slug}/planning-manifest.json. Write auto-creates any missing parent directories, and the shipped allowlist already covers Write(.claude/quality/sessions/**) — so the folder pops into existence without a permission prompt, regardless of OS or whether the working-dir reference is relative or absolute. (Calling mkdir adds a Bash permission round-trip with no benefit; previous skill versions did, which caused intermittent prompts on Windows where path resolution sometimes expanded to absolutes outside the allowlist.)