# Cowork-LFCS Cheat Sheet Last updated: 2026-05-06 — cowork-lfcs Quick reference for getting the most out of cowork-lfcs in The Window. Pin this. If something below is wrong or stale, fix it — append-only doesn't apply (this isn't a log). --- ## Session start — say this, skip the dance - **"job 26XX"** — fastest opener. I load the per-job CLAUDE.md + brief + registers and we go. - **"no boot, quick Q"** — skip inheritance for a one-off question. - **"new job: 26XX [name] — [scope]"** — fires `lfcs-project-init` orchestrator (scaffold → text-pass → spec-summarise → BOQ parse → bid-prep → pre-call questions → incl/excl → Airtable audit). If you don't say a job, I'll ask. Save us the round trip. --- ## Trigger phrases — use these verbatim, they fire skills | Say this | Fires | |---|---| | `new job: 26XX [name]` | lfcs-project-init (full orchestrator) | | `scaffold job 26XX` | lfcs-job-scaffold (folder + brief + per-job CLAUDE.md) | | `text-pass drawings` | lfcs-drawing-extract-text | | `vision-pass drawings` | lfcs-drawing-extract-vision (run AFTER text-pass) | | `parse the BOQ` | lfcs-boq-parse | | `summarise this spec` | lfcs-spec-summarise (TfNSW, AS/NZS, council) | | `draft bid prep` | lfcs-bid-prep-doc | | `pre-call questions` | lfcs-precall-questions | | `incl/excl draft` | lfcs-incl-excl-draft | | `sync to Airtable` | lfcs-airtable-sync (auto-runs as final step of others) | If a phrase doesn't appear above, the skill probably doesn't exist yet — I'll tell you, won't pretend. --- ## Lane discipline — send the right thing here **Cowork-LFCS does (this surface):** Bid prep, quotes, RFIs, variations, programmes, subby briefs, defects registers, formal correspondence, longer drafts, Airtable writes, spec summaries, pricing history entries. **Send elsewhere:** - Site/voice/photo intake / quick docket scan → **Hermes via Telegram** - Strategic / cross-project / priority drift / weekly grilling → **cowork-hq** - Repo code, RateRight, anything `git`-shaped → **claude-code-rr or terminal** - Heavy compute batch (vision-pass on 20+ PDFs, mass parse, cron) → **Claude Code CLI dispatch** — don't make Rocky wait synchronously --- ## What you're probably not doing but should **1. Pricing history — the flywheel.** Every time we land on a price (won or lost), write a per-line MD at `Operations/lfcs-standards/pricing-history/{job}-{section}-{slug}.md`. Schema in `pricing-history/README.md`. Element values match `element-taxonomy.md`. Next quote, I grep that folder before guessing. Right now this folder is undernourished — fix it as we close out 2602 and 2626. **2. Spec summaries.** Any time you hand me a TfNSW R-spec, AS/NZS, council spec, Sydney Water doc — say "summarise this spec." Output lands in `lfcs-standards/specs/` and Airtable Specifications.Notes. Read once, reuse forever. Currently underused. **3. Per-job CLAUDE.md updates mid-job.** When a pattern emerges on a live job (e.g. "PM at this council always wants X format"), append it to that job's `CLAUDE.md`. Next session inherits. Don't keep it in your head. **4. Concept notes for recurring patterns.** If you see the same thing twice across jobs, ask me to write a concept note at `lfcs-standards/concepts/`. Wikilink it from per-job CLAUDE.mds. This is how the standards library compounds. **5. Vision-pass after text-pass on every bid-critical job.** Text alone = Confidence: Medium. Vision validates → High. Vision also catches what text missed (notes blocks, callouts, hatches). Mandatory per Phase 0 in the LFCS Bid System Plan. Skip = bidding blind. **6. Pre-pricing grill.** End of `project-init` hands off to me to grill you on assumptions before pricing. Don't skip it. That's where the bad assumption gets caught for $3k instead of $30k. **7. Reference fixtures as quality bars.** Before locking a new bid pack, sanity-check it against 2602 Munmorah Bridge or 2626 Mack Civil — whichever is closer. If your output is thinner than those, it's not done. **8. Manual commit at session close** for critical writes. Auto-sync is 30 min on the VPS, but if you've moved a $400k bid quote, prompt me to push now. --- ## Write protocol — what gets logged automatically Every session I touch, three writes minimum: 1. `01_Daily/{today}.md` — `## HH:MM — cowork-lfcs — {title}` 2. `_Brain/_Log.md` — one-liner with backlink 3. Job's `_Log.md` if I touched a job folder You don't need to prompt these — they fire on substantive work. If a session was pure conversation (like this one), I may skip. Tell me to log if you want it captured. --- ## Hard don'ts — never, even if you ask twice - No deletions (move to `_Archive/`) - No body content edits without explicit ask - No new top-level folders without approval - No sensitive data in notes (passwords, card numbers, tokens) — reference by name - No content invention — "I don't know" is a valid answer - No SMS re-enable anywhere without explicit approval - No Airtable record deletes — `Status = Superseded` instead --- ## The Window pattern (7:00–8:30 PM AEST) **Good queue items:** bid prep review, RFI drafts to send, variation drafts, weekly review, pricing decisions, spec summaries, defects register reviews, subby brief drafts. **Don't queue here:** quick site lookups (Hermes can do during the day), repo code (use the terminal in deep-work block 8:30–11:00). --- ## Reference fixtures — the gold standard - **2602 Munmorah Bridge** — TfNSW Bridge FRP Subcontract pattern (TCE supply, IFI→IFC drift, AS5100). Active Bid `recGdAkZHQklVAgUR` ($407,870 ex GST CCC v1). - **2626 Mack Civil Stormwater Pit EXA01A-08** — TfNSW R0220 Pit pattern (FRP-install-only, R11+R53). Active Bid `recJFeA83SRGOne1s` ($43,143 ex GST rev5). Every new skill must reproduce or improve their outputs before being marked production-ready. --- ## Skills not built yet (don't ask, I'll tell you no) `lfcs-boq-cross-check`, `lfcs-pricing-estimator`, `lfcs-bid-vs-qs-compare`, `lfcs-pricing-history-lookup`, `lfcs-rfi-drafter`, `lfcs-variation-drafter`, `lfcs-defects-register`, `lfcs-subby-brief`, `lfcs-programme-drafter`, `lfcs-progress-claim`, `lfcs-uploads-cleanup`. If you find yourself doing one of these manually three times, prompt me: "build the skill." I'll spec it. --- ## When in doubt Ask. One question, not five. Check `_System/CLAUDE.md` and `_Brain/CLAUDE.md` first — usually the answer is there.