qwen-base 1.0.0

package/src/commands/orientation/tasks/deep-why.md

@@ -0,0 +1,132 @@
+<purpose>
+Excavate the operator's root motivation through a 5-layer "but why?" process. Each layer peels back a surface answer to find the one beneath it, arriving at a foundational Deep Why statement.
+</purpose>
+
+<user-story>
+As an operator, I want to uncover my deepest motivation for doing what I do, so that my work connects to something real and sustaining rather than external pressure or habit.
+</user-story>
+
+<when-to-use>
+- Phase 1 of new orientation
+- Operator chose to reorient their Deep Why specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="setup" priority="first">
+<if condition="previous orientation exists">
+> Your previous Deep Why was:
+> *"{previous statement}"*
+>
+> We're going to excavate fresh. You can land in the same place or somewhere new. Either is fine.
+</if>
+
+> **Layer 1 of 5**
+>
+> Why do you do what you do? Not the business answer. Not the resume answer. The real one.
+
+**Wait for response.**
+</step>
+
+<step name="layer_2">
+Reflect back what the operator said in Layer 1 — one sentence, their words not yours.
+
+> You said: "{reflection}"
+>
+> **Layer 2 of 5**
+>
+> But why does that matter to you?
+
+**Wait for response.**
+</step>
+
+<step name="layer_3">
+Reflect back Layer 2.
+
+> You said: "{reflection}"
+>
+> **Layer 3 of 5**
+>
+> But why?
+
+If the answer feels surface-level or performative, push: "That sounds like something you'd say to someone else. What's the version you'd say to yourself at 2am?"
+
+**Wait for response.**
+</step>
+
+<step name="layer_4">
+Reflect back Layer 3.
+
+> You said: "{reflection}"
+>
+> **Layer 4 of 5**
+>
+> Why does that drive you more than anything else?
+
+**Wait for response.**
+</step>
+
+<step name="layer_5">
+Reflect back Layer 4.
+
+> You said: "{reflection}"
+>
+> **Layer 5 of 5 — the root**
+>
+> If everything else was stripped away — the business, the tools, the audience — what's left? What's the thing that would still make you get up and build?
+
+**Wait for response.**
+</step>
+
+<step name="synthesize">
+Now synthesize all 5 layers into a single Deep Why statement.
+
+1. Read back all 5 layers
+2. Draft a one-sentence synthesis that captures the root, not just Layer 5 but the thread through all layers
+3. Present it:
+
+> Here are your 5 layers:
+> 1. {layer 1}
+> 2. {layer 2}
+> 3. {layer 3}
+> 4. {layer 4}
+> 5. {layer 5}
+>
+> **Your Deep Why:**
+> *"{synthesized statement}"*
+>
+> **[1] That's it** — lock it in
+> **[2] Close but needs tweaking** — let me adjust the wording
+> **[3] Not right** — let me redo a layer
+
+If [2]: Let operator edit the statement directly.
+If [3]: Ask which layer to redo, then resume from that layer.
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Deep Why is locked.
+
+Return to parent workflow with:
+- `layers`: array of 5 layer answers
+- `statement`: final approved synthesis
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Deep Why data: 5 layers + synthesized statement, ready for operator.json.
+</output>
+
+<acceptance-criteria>
+- [ ] All 5 layers answered by operator (not generated)
+- [ ] Each layer reflected back before asking the next
+- [ ] Surface answers challenged when detected
+- [ ] Synthesis captures the thread, not just layer 5
+- [ ] Operator approved the final statement
+</acceptance-criteria>

package/src/commands/orientation/tasks/elevator-pitch.md

@@ -0,0 +1,115 @@
+<purpose>
+Synthesize the operator's identity into a 4-floor elevator pitch — a 30-second statement of who they are, what they do, why it matters, and where they're going. Built on top of Deep Why, North Star, and Values.
+</purpose>
+
+<user-story>
+As an operator, I want a clear, statable pitch for who I am and what I'm about, so that I can articulate my value to anyone in 30 seconds without fumbling.
+</user-story>
+
+<when-to-use>
+- Phase 4 of new orientation (after Key Values)
+- Operator chose to reorient their Elevator Pitch specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="frame_the_exercise" priority="first">
+<if condition="previous orientation exists">
+> Your previous pitch was:
+> *"{previous pitch}"*
+</if>
+
+> Your foundation so far:
+> - **Deep Why:** {statement}
+> - **North Star:** {metric}
+> - **Values:** {v1}, {v2}, {v3}, {v4}, {v5}
+>
+> An elevator pitch has 4 floors. Each floor is one sentence:
+>
+> **Floor 1** — Who you are (identity, not job title)
+> **Floor 2** — What you do (the work, in plain language)
+> **Floor 3** — Why it matters (the impact)
+> **Floor 4** — What's next (the vision or the ask)
+>
+> Let's build each floor. Don't try to be clever — try to be clear.
+</step>
+
+<step name="floor_1">
+> **Floor 1: Who are you?**
+>
+> Not your job title. Not your company. If you met someone at a party and they asked "what are you about?" — what's the one-sentence answer?
+
+**Wait for response.**
+</step>
+
+<step name="floor_2">
+Reflect Floor 1 back, then:
+
+> **Floor 2: What do you do?**
+>
+> The work itself. What does your day look like when it's going well? One sentence.
+
+**Wait for response.**
+</step>
+
+<step name="floor_3">
+Reflect Floor 2 back, then:
+
+> **Floor 3: Why does it matter?**
+>
+> Who benefits and how? This connects to your Deep Why. One sentence.
+
+**Wait for response.**
+</step>
+
+<step name="floor_4">
+Reflect Floor 3 back, then:
+
+> **Floor 4: What's next?**
+>
+> Where is this going? What's the thing you're building toward? This connects to your North Star. One sentence.
+
+**Wait for response.**
+</step>
+
+<step name="assemble_and_refine">
+Assemble the full pitch from all 4 floors. Read it as one continuous statement.
+
+> ## Your Elevator Pitch
+>
+> *"{floor1} {floor2} {floor3} {floor4}"*
+>
+> Read it out loud. Does it sound like you?
+>
+> **[1] That's me — lock it in**
+> **[2] Reword a floor** — tell me which one
+> **[3] Start over** — the whole thing feels off
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Elevator Pitch is locked.
+
+Return to parent workflow with:
+- `pitch`: full assembled pitch
+- `floors`: object with floor_1 through floor_4
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Elevator Pitch data: 4 floors + assembled pitch, ready for operator.json.
+</output>
+
+<acceptance-criteria>
+- [ ] Each floor answered individually by operator
+- [ ] Full pitch reads as one coherent 30-second statement
+- [ ] Floor 3 connects to Deep Why
+- [ ] Floor 4 connects to North Star
+- [ ] Operator confirmed it sounds like them
+</acceptance-criteria>

package/src/commands/orientation/tasks/initiatives.md

@@ -0,0 +1,98 @@
+<purpose>
+Guide the operator through defining or reviewing goal-oriented initiatives aligned to their North Star. Each initiative is a measurable strategic objective, not an entity or project.
+</purpose>
+
+<user-story>
+As an operator who has completed their identity profile, I want to define the strategic objectives my work serves, so that every project and task traces back to a clear goal.
+</user-story>
+
+<when-to-use>
+- Phase 6 of new orientation (after Surface Vision)
+- Operator chose to reorient their initiatives specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="ground_in_profile" priority="first">
+<if condition="previous initiatives exist">
+Pull current initiatives via base_list_projects(type="initiative") and display them:
+
+> ## Current Initiatives
+>
+> {For each initiative: title, description, status, project count}
+>
+> We'll review each one against your North Star.
+</if>
+
+<if condition="no initiatives exist">
+> Your North Star: *"{north_star_metric}"*
+> Your Deep Why: *"{deep_why_statement}"*
+>
+> Initiatives are the strategic objectives that move you toward the North Star. NEVER confuse them with businesses or entities — an initiative is a measurable goal.
+>
+> Example: Not "C&C Strategic Consulting" but "Build C&C to $7k/month MRR"
+>
+> What are the 2-4 major objectives you're working toward right now? Think in terms of outcomes, not labels.
+</if>
+
+**Wait for response.**
+</step>
+
+<step name="define_each_initiative">
+For each initiative the operator names:
+
+> **Initiative: "{title}"**
+>
+> 1. How does this connect to your North Star?
+> 2. What's the key metric or success criteria?
+> 3. Is there a timeframe?
+
+Capture: title, description, priority, category, metric, timeframe.
+
+NEVER let an initiative through that is actually an entity (person, business, org). Push back: "That's a business name, not a goal. What's the measurable objective for that business?"
+
+**Wait for response between each initiative.**
+</step>
+
+<step name="confirm_and_write">
+Present all initiatives:
+
+> ## Your Initiatives
+>
+> 1. **{title}** — {description} ({metric}, {timeframe})
+> 2. **{title}** — {description} ({metric}, {timeframe})
+> ...
+>
+> **[1] Lock these in**
+> **[2] Add another**
+> **[3] Edit one**
+> **[4] Remove one**
+
+When locked, write each initiative via base_add_project(type="initiative") with full metadata.
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Initiatives are locked.
+
+Return to parent workflow with:
+- `initiatives`: array of created initiative IDs and titles
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Initiatives created in Apex via MCP. Each has title, description, priority, category, metric alignment to North Star.
+</output>
+
+<acceptance-criteria>
+- [ ] Each initiative is a measurable goal, not an entity
+- [ ] Each initiative connects to the North Star
+- [ ] Written via base_add_project MCP, not manual file edits
+- [ ] Operator approved the final set
+</acceptance-criteria>

package/src/commands/orientation/tasks/key-values.md

@@ -0,0 +1,130 @@
+<purpose>
+Guide the operator through identifying and ranking their top 5 personal values — the core principles they operate by. The constraint of exactly 5 forces prioritization and clarity.
+</purpose>
+
+<user-story>
+As an operator, I want to be clear on my top 5 operating principles, so that I can make decisions faster and stay aligned when things get chaotic.
+</user-story>
+
+<when-to-use>
+- Phase 3 of new orientation (after North Star)
+- Operator chose to reorient their Key Values specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="context_and_brainstorm" priority="first">
+<if condition="previous orientation exists">
+> Your previous values were:
+> 1. {v1} — {meaning1}
+> 2. {v2} — {meaning2}
+> 3. {v3} — {meaning3}
+> 4. {v4} — {meaning4}
+> 5. {v5} — {meaning5}
+</if>
+
+> Your Deep Why: *"{deep_why_statement}"*
+> Your North Star: *"{north_star_metric}"*
+>
+> Values are the principles you actually operate by — not aspirational ones you wish you had. Think about the last time you made a hard decision. What did you lean on?
+>
+> Give me 7-10 values that feel true. Don't overthink it — we'll narrow down.
+
+**Wait for response.**
+</step>
+
+<step name="gut_check">
+Before cutting, reflect each value back with a personalized one-line description based on what you know about the operator. This helps them see what each value actually means to them, not just the word.
+
+> Here's what I'm hearing from you:
+>
+> 1. **{Value}** — {personalized description based on context}
+> 2. **{Value}** — {personalized description}
+> ...
+>
+> Is anything missing that you'd fight for if challenged? Or are these the ones?
+>
+> **[1] These are the ones — let's cut to 5**
+> **[2] I want to add 1-2 more, then cut**
+
+**Wait for response.**
+</step>
+
+<step name="narrow_to_five">
+Force the cut. ALWAYS show the personalized description alongside each value — never list bare value names.
+
+> Now the hard part — cut to 5. The ones that survive are the ones you'd defend if someone challenged them.
+>
+> Which ones can you live without? Drop them one at a time until you're at 5.
+
+If operator struggles, offer a forcing question: "If you could only teach your kids 5 principles about how to live, which of these make the cut?"
+
+**Wait for response.**
+</step>
+
+<step name="rank">
+Present values WITH their descriptions, then ask for ranking:
+
+> 1. **{Value}** — {description}
+> 2. **{Value}** — {description}
+> ...
+>
+> Now rank them 1-5. #1 is the one that wins when two values conflict.
+
+**Wait for response.**
+</step>
+
+<step name="add_meaning">
+For each value in ranked order:
+
+> **{Value #N}: {value name}**
+> In one sentence — what does this look like in practice for you? Not the dictionary definition. How does this value show up in your daily decisions?
+
+Iterate through all 5, waiting for each response.
+
+**Wait for each response.**
+</step>
+
+<step name="confirm_and_lock">
+Present the complete values list:
+
+> ## Your 5 Key Values
+>
+> 1. **{v1}** — {meaning}
+> 2. **{v2}** — {meaning}
+> 3. **{v3}** — {meaning}
+> 4. **{v4}** — {meaning}
+> 5. **{v5}** — {meaning}
+>
+> **[1] Lock it in**
+> **[2] Swap a value**
+> **[3] Rerank**
+> **[4] Reword a meaning**
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Key Values are locked.
+
+Return to parent workflow with:
+- `values`: array of 5 objects (rank, value, meaning)
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Key Values data: 5 ranked values with practical meanings, ready for operator.json.
+</output>
+
+<acceptance-criteria>
+- [ ] Started with 7-10 brainstormed values
+- [ ] Narrowed to exactly 5
+- [ ] Ranked 1-5 with explicit prioritization
+- [ ] Each value has a practical meaning (not dictionary definition)
+- [ ] Operator approved the final list
+</acceptance-criteria>

package/src/commands/orientation/tasks/new-orientation.md

@@ -0,0 +1,162 @@
+<purpose>
+Orchestrate a full first-time orientation through all 5 phases: Deep Why, North Star, Key Values, Elevator Pitch, Surface Vision. Composes each phase task sequentially, passing context forward, and produces operator.json at the end.
+</purpose>
+
+<user-story>
+As an operator setting up my workspace for the first time, I want a guided walkthrough of my identity anchors, so that my initiatives, projects, and tasks align to who I am and where I'm going.
+</user-story>
+
+<when-to-use>
+- No operator.json exists yet
+- Entry point routes here when operator chooses [1] Begin orientation
+</when-to-use>
+
+<context>
+@../templates/operator-json.md
+</context>
+
+<steps>
+
+<step name="set_expectations" priority="first">
+Brief the operator on what's coming.
+
+> You'll go through 5 exercises. Each builds on the last:
+>
+> 1. **Deep Why** — excavate your root motivation (5 layers)
+> 2. **North Star** — define the one metric everything points at
+> 3. **Key Values** — narrow to your top 5 operating principles
+> 4. **Elevator Pitch** — synthesize who you are in 30 seconds
+> 5. **Surface Vision** — anchor a tangible picture of the future
+>
+> Take your time. There's no wrong answers, but surface-level ones won't serve you.
+>
+> **[1] Let's go — start with Deep Why**
+> **[2] I need a minute — come back to this**
+
+If [2]: Exit gracefully. Orientation can resume anytime via `/base:orientation`.
+
+**Wait for response.**
+</step>
+
+<step name="phase_1_deep_why">
+Load and execute @deep-why.md
+
+Pass no prior context (this is the first phase).
+
+When deep-why.md completes and locks its result, capture the output (layers + statement) and continue here.
+</step>
+
+<step name="phase_2_north_star">
+Load and execute @north-star.md
+
+Pass context: the Deep Why statement from Phase 1.
+
+When north-star.md completes and locks its result, capture the output (metric + timeframe + rationale) and continue here.
+</step>
+
+<step name="phase_3_key_values">
+Load and execute @key-values.md
+
+Pass context: Deep Why statement + North Star metric.
+
+When key-values.md completes and locks its result, capture the output (5 ranked values with meanings) and continue here.
+</step>
+
+<step name="phase_4_elevator_pitch">
+Load and execute @elevator-pitch.md
+
+Pass context: Deep Why statement + North Star metric + Key Values list.
+
+When elevator-pitch.md completes and locks its result, capture the output (4 floors + full pitch) and continue here.
+</step>
+
+<step name="phase_5_surface_vision">
+Load and execute @surface-vision.md
+
+Pass context: Deep Why statement + North Star metric + Key Values + Elevator Pitch.
+
+When surface-vision.md completes and locks its result, capture the output (scenes + summary) and continue here.
+</step>
+
+<step name="synthesize_and_write">
+All 5 phases complete. Synthesize into operator.json.
+
+1. Read @../templates/operator-json.md for schema
+2. Populate all fields from captured phase outputs
+3. Write to `.base/operator.json`
+4. Display the complete profile in a clean summary:
+
+> ## Your Operator Profile
+>
+> **Deep Why:** {statement}
+> **North Star:** {metric} ({timeframe})
+> **Values:** {value1}, {value2}, {value3}, {value4}, {value5}
+> **Elevator Pitch:** {full pitch}
+> **Surface Vision:** {summary}
+>
+> Profile saved to `.base/operator.json`.
+>
+> **[1] Looks right — done**
+> **[2] Something's off — let me adjust a section**
+
+If [2]: Ask which section, load that specific task for revision, then re-write operator.json.
+
+**Wait for response.**
+</step>
+
+<step name="phase_6_initiatives">
+Load and execute @initiatives.md
+
+Pass context: Full operator profile (Deep Why, North Star, Values).
+
+When initiatives.md completes and locks its result, capture the output (initiative IDs and titles) and continue here.
+</step>
+
+<step name="phase_7_project_mapping">
+Load and execute @project-mapping.md
+
+Pass context: Created initiatives from Phase 6.
+
+When project-mapping.md completes and locks its result, capture the output (mapping counts, PAUL sync counts) and continue here.
+</step>
+
+<step name="phase_8_task_seeding">
+Load and execute @task-seeding.md
+
+Pass context: Initiative → Project mapping from Phase 7.
+
+When task-seeding.md completes and locks its result, capture the output (task counts) and continue here.
+</step>
+
+<step name="orientation_complete">
+All 8 phases complete. Display final summary:
+
+> ## Orientation Complete
+>
+> **Operator Profile:** `.base/operator.json`
+> - Deep Why, North Star, Values, Pitch, Vision — locked
+>
+> **Initiatives:** {count} defined, aligned to North Star
+> **Projects:** {mapped_count} mapped to initiatives, {unparented_count} unparented
+> **PAUL Satellites:** {paul_synced} synced
+> **Tasks:** {tasks_created} seeded across {projects_with_tasks} projects
+>
+> You're oriented. Run `/base:orientation` anytime to review or reorient.
+</step>
+
+</steps>
+
+<output>
+Complete workspace orientation: operator.json populated, initiatives defined, projects mapped, PAUL synced, tasks seeded.
+</output>
+
+<acceptance-criteria>
+- [ ] All 8 phase tasks executed in order
+- [ ] Each phase locked before advancing to next
+- [ ] Context passed forward between phases
+- [ ] operator.json written with all fields populated
+- [ ] Initiatives created via Apex MCP
+- [ ] Projects mapped to initiatives with PAUL data synced
+- [ ] Tasks seeded under projects
+- [ ] Operator reviewed and approved at each phase
+</acceptance-criteria>