Skip to content

Workflows

Updated: 2026-06-05

End-to-end workflows for each department. Each workflow shows who does what, where agent outputs go, and where humans must make a decision before work continues.

GATE = human must review and decide before the next step proceeds.

Dev Workflow

Slack channel: #dev
Owners: Terry, Teammate A Operating rules: Agile Gates, Secure Coding and Testing, UI Guidelines

1. Opportunity identified
   - Discuss scope in #dev or weekly all-hands
   - Capture target user, problem, expected value, and likely estimate band

2. GATE: Intake review
   - Decision: build / research / revise / drop
   - Terry decides company priority
   - Teammate A confirms dev feasibility for build work

3. plan: [project description]
   - Planner writes wiki/dev/[project]/spec.md
   - Required output: MVP, acceptance criteria, UI risks, security risks,
     estimate band, proposed token budget, and out-of-scope items
   - Posts spec summary to #dev

4. GATE: Spec review
   - Teammate A (+ Terry for large or client-facing projects) reviews spec
   - Decision: approved / revise / drop / split
   - Must be explicit: "approved" in #dev before coding starts

5. build: [approved task or round from spec]
   - Implementer writes code to repo
   - Required output: approved round reference, changed files, known limits,
     and confirmation that scope did not expand
   - Posts diff summary to #dev

6. GATE: Build scope check
   - Human checks whether the build stayed inside the approved round
   - Decision: continue / revise / split / stop

7. test: [approved task or release candidate]
   - Tester reads spec and runs acceptance checks
   - Tester runs simple security checks from Secure Coding and Testing
   - Tester writes wiki/dev/[project]/defects.md
   - Required output: acceptance results, security results, defects by severity,
     untested areas, and release recommendation

8. GATE: Test review
   - Critical/high defects block release
   - Medium defects require owner decision
   - Decision: ship / hold / revise

9. Repeat build and test rounds until all approved acceptance criteria pass

10. GATE: Release approval
    - Teammate A reviews final state
    - Terry approves client-facing releases
    - Decision: ship / hold

11. Retro
    - Log what changed, what was abandoned, and what was learned
    - Update decisions.md, status.md, and reusable knowledge if relevant

Consulting Workflow

Slack channel: #consulting
Owners: Terry, Teammate B

1. Engagement identified from Sales pipeline or direct contact
   - Create project in wiki/consulting/[project]/

2. consult: create brief for [client] - [scope]
   - Consultant writes wiki/consulting/[project]/brief.md
   - Posts brief summary to #consulting

3. GATE: Key message sign-off
   - Terry reads brief and approves the core message
   - Nothing proceeds without this; a wrong key message wastes downstream work

4. scout: [research topics for this project]
   - Scout writes research pages to wiki/research/
   - Posts findings to #consulting

5. consult: write insights and storyline for [project]
   - Consultant reads research + brief and writes insights.md
   - Posts storyline to #consulting

6. GATE: Storyline sign-off
   - Terry reviews whether each beat proves the key message
   - Decision: approve / revise
   - No deck outline until storyline is approved

7. consult: write deck outline for [project]
   - Consultant writes wiki/consulting/[project]/deck-outline.md
   - Posts outline to #consulting

8. GATE: Deck outline review
   - Terry + Teammate B review slide-by-slide
   - Decision: approve / revise

9. Render deck
   - Human delivers to client

Sales Workflow

Slack channel: #sales
Owner: Teammate B (Terry on key accounts) Operating rule: Sales owns both offense and defense in v1. See Sales Offense and Defense.

1. Lead identified
   sales: add lead [name], [company], [service interest], [stage]
   - Sales agent updates wiki/sales/pipeline.md
   - Posts updated pipeline to #sales

2. Offense asset needed
   sales: draft outreach/follow-up/proposal note for [lead]
   - Sales agent writes wiki/sales/outreach/[lead].md or updates pipeline notes
   - Posts draft to #sales

3. Defense asset needed
   sales: draft objection response / FAQ / intro copy / case-study outline
   - Sales agent writes the relevant sales or company wiki draft
   - Posts draft to #sales

4. GATE: Outreach review and send
   - Teammate B edits draft as needed
   - Human always sends; agents never send external emails

5. Response received
   sales: update [lead] stage to [new stage], note: [context]

6. Lead reaches "qualified"
   - Discuss scope in #sales or with Terry
   - GATE: Go/no-go on engagement (Terry + Teammate B)
   - If yes: create consulting brief or dev project intake

7. Won or lost
   - Won: move lead to Won table in pipeline.md and hand off to delivery
   - Lost: log reason in pipeline.md and set revival date if relevant

Finance Workflow

Slack channel: #finance
Owner: Terry

1. Expense occurs
   finance: log [amount] [category] [description] [month]
   - Finance agent updates wiki/finance/[YYYYMM]/budget.md
   - Posts updated budget to #finance

2. Invoice needed
   finance: draft invoice for [client], [amount], [project]
   - Finance agent writes wiki/finance/[YYYYMM]/invoices.md
   - Posts draft invoice to #finance

3. GATE: Invoice review and send
   - Terry reviews draft
   - Human always sends invoices; agent drafts only

4. Monthly budget summary
   finance: budget summary for [YYYYMM]
   - Finance agent posts actuals vs targets to #finance
   - Terry reviews and flags any department over cap

Research Workflow

Slack channel: any; research supports all departments Available to: everyone

1. Topic needed for any department
   scout: [topic or question]
   - Scout searches Tavily and writes wiki/research/[topic]/notes.md
   - Posts 5-bullet summary to the triggering channel

2. Analysis needed on existing wiki knowledge
   sage: [question]
   - Sage reads wiki/index.md and relevant pages
   - Posts structured analysis with recommendation to the triggering channel

3. Chained research + analysis
   scout: [topic]
   sage: [question based on what Scout found]

Cross-Department Decision Log

When a significant decision is made, log it:

  • In the relevant wiki page (decisions.md for dev projects, brief.md for consulting, pipeline.md for sales)
  • With who decided, what was decided, date, and why
  • Using explicit decision words from Agile Gates

This prevents re-litigating the same decision and gives agents context when picking up a project.