---
name: linear-company-operator
description: Use when operating Linear as Sam/Nancy's company task system: creating or restructuring projects, milestones, cycles, views, revenue priorities, Sam decision tasks, Nancy execution tasks, and proof-based follow-through.
---

# Linear Company Operator

Use Linear as the company operating system, not a task dump.

## Core model

- **Projects** = money/outcome lanes with clear end states.
- **Milestones** = phases inside a project: `Proof / Audit`, `Ship / Outreach`, `Revenue / Conversion`.
- **Cycles** = this sprint / this-week execution only; backlog stays out of the current cycle.
- **Issues** = atomic next actions with one owner and proof required.
- **Views** = durable decision/operating surfaces.

## Sam vs Nancy assignment

Assign **Sam** only leverage/blocker tasks Nancy cannot do:
- decisions changing direction
- approvals for external sends/posts/config/restarts
- intros, relationship moves, customer/client replies
- access, credentials, billing, account-owner actions
- public proof confirmation when Nancy lacks access

Sam tasks should start with `[Needs Sam]`, include answer choices when possible, and include an explicit @Sam comment so the request reaches Sam's Linear inbox. Do not rely on assignment alone.

Assign **Nancy** execution/proof tasks:
- research, audits, code/content/build work
- QA and proof capture
- social/content production
- follow-up after Sam decisions
- conversion system setup

## Required Linear surfaces

Maintain these views when possible:
- `Sam Answer Desk`: assignee Sam, active/not done, `[Needs Sam]` or blocker/approval/access decision.
- `Nancy Queue`: assignee Nancy, active/backlog, grouped by project.
- `This Week / Cycle`: current cycle only, sorted by priority/estimate.
- `Revenue Now`: issues/projects directly tied to leads, sales, posts, offers, outreach, conversion.
- `Blocked`: waiting on access, approval, external proof, credential, or runtime blocker.

## Project setup checklist

For each money/outcome project:
1. Set a concise summary and outcome-oriented description.
2. Add three milestones: `Proof / Audit`, `Ship / Outreach`, `Revenue / Conversion`.
3. Create one Nancy-owned audit/proof issue.
4. Create at most one Sam-owned blocker/decision issue.
5. Put only current sprint issues into the current cycle.
6. Require proof before Done: URL, screenshot, file, test/build result, public post link, Linear comment, or artifact path.

## Prioritization

Rank by:
1. direct revenue proximity
2. speed to ship
3. proof clarity
4. blocker removal power
5. fit with current priority stack

Default priority stack:
1. DDHG / Habit Garden developer acquisition
2. Creature Beach / Shelly Shop content and conversion
3. Nancy/OpenClaw reliability where it blocks execution
4. AI Business Boomer lead funnel and SEO
5. Panimate pro funnel / first customers
6. Dishrated validation/scoring

## Operating loop

0. Check recent Linear comments/mentions first. If Sam commented or @mentioned Nancy in a ticket, reply in that Linear thread before summarizing in Telegram.
1. Capture raw intake in Telegram or quick Linear issue.
2. Convert executable work into Nancy issues.
3. Convert blockers into `[Needs Sam]` issues with answer choices.
   - Add a short @Sam comment explaining the exact decision/access/action needed and the recommended choice.
4. Review current cycle; keep it small.
5. When Sam answers, create/update Nancy execution issue and mark Sam blocker Done.
6. Do not mark work Done without proof in Linear or a linked artifact.

## Comment response rule

- Linear comments are not optional side-channel chatter; they are part of the task record.
- If Sam asks status in Linear, answer in Linear with current state, blocker, next action, and proof gap.
- If Sam changes direction in Linear, acknowledge it in Linear and update the issue title/description/project/status when appropriate.
- If Nancy needs Sam's help, @mention Sam in the Linear comment on that exact issue; this is required for Sam-owned blockers and current-cycle decisions.
- Because the current API key belongs to Sam's account, API-created comments may visually show as Sam; prefix with `Nancy response:` until Nancy has her own Linear API identity.