Field Notes CRM

# Field Notes CRM

A local-first workspace for turning client notes into a clean solo-operator pipeline.

## Project Brief
- **Raw idea:** Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
- **Target user:** A solo consultant who wants one private browser workspace before opening GitHub issues.
- **Problem:** Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
- **Goals:** Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
- **Non-goals:** No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
- **Constraints:** All user data stays in localStorage on the current browser. Demo data is fake.
- **Tech stack:** Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
- **Deployment target:** Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
- **Success criteria:** A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

## Agent Workflow
### Planner
Turn a rough idea into a clear product brief and buildable scope.

- [x] **Project brief drafted** - Problem, target user, goals, non-goals, and constraints are written. (Fake demo brief is complete.)
- [x] **MVP scope defined** - The first release avoids paid APIs, login, cloud storage, and backend requirements. (Scope excludes integrations.)
- [ ] **Risks listed** - Known blockers and assumptions are visible before build work.

Notes: Lock the project intent before implementation starts.

### Builder
Create the app structure, local data model, core workflows, and verification path.

- [x] **Repository structure planned** - Folders, scripts, and local-only data boundaries are identified. (Next.js + localStorage only.)
- [ ] **Test plan listed** - Domain and UI checks are documented before coding.
- [ ] **Static deployment path noted** - Free deployment targets are named without adding cloud data services.

Notes: Implementation work should stay local-first and reversible.

### Critic
Review the plan and build for unclear scope, weak evidence, generic UX, and hidden data risks.

- [x] **Privacy reviewed** - No paid API, login, backend, upload, analytics, or cloud database dependency exists. (Local-only constraint visible.)
- [ ] **UX reviewed** - The workspace is informative, professional, and non-generic.
- [ ] **Readiness score inspected** - Score factors are deterministic and visible.

Notes: The critic should challenge vague claims before GitHub handoff.

### Docs
Prepare project documentation for GitHub readers and future agent sessions.

- [x] **README outline ready** - Purpose, features, stack, setup, checks, and deployment are documented. (Fake demo README outline.)
- [x] **Decision log ready** - Important product and technical decisions are recorded. (Local-first decision exists.)
- [ ] **Obsidian export ready** - Current state can be exported to Markdown.

Notes: Docs explain the product, local setup, constraints, and deployment separation.

### Review
Confirm the project is GitHub-ready before deployment or public sharing.

- [x] **CI checks identified** - Lint, typecheck, tests, and build are listed as blockers. (Quality scripts named.)
- [ ] **GitHub readiness checked** - Repo hygiene, README, license intent, and PR path are reviewed.
- [x] **Deployment notes separated** - Vercel, Cloudflare, or Netlify are hosting targets, not source control. (GitHub and deploy targets separated.)

Notes: Review checks are separate from deployment platforms.

## GitHub Readiness Score
Score: 82/100 (Working)

- Project Brief completeness: 25/25 - 11/11 brief fields are filled.
- Agent workflow completion: 16/30 - 8/15 checklist items are complete.
- Documentation readiness: 15/15 - 4/4 documentation signals are present.
- GitHub setup readiness: 11/15 - 3/4 GitHub readiness signals are present.
- Deployment notes readiness: 10/10 - 2/2 deployment separation signals are present.
- Review and log hygiene: 5/5 - 2 log entries recorded.

## Codex Prompts
### Planner prompt for Field Notes CRM

```text
You are the Planner agent for Field Notes CRM.

Project brief:
Name: Field Notes CRM
Tagline: A local-first workspace for turning client notes into a clean solo-operator pipeline.
Raw idea: Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
Target user: A solo consultant who wants one private browser workspace before opening GitHub issues.
Problem: Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
Goals: Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
Non-goals: No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
Constraints: All user data stays in localStorage on the current browser. Demo data is fake.
Tech stack: Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
Deployment target: Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
Success criteria: A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

Current checklist:
- [x] Project brief drafted: Problem, target user, goals, non-goals, and constraints are written. Evidence: Fake demo brief is complete.
- [x] MVP scope defined: The first release avoids paid APIs, login, cloud storage, and backend requirements. Evidence: Scope excludes integrations.
- [ ] Risks listed: Known blockers and assumptions are visible before build work.

Instruction:
Work only on the Planner stage. Keep the project local-first. No paid APIs, no OpenAI API, no login, no required backend, no cloud database, and no user-data upload.
```

### Builder prompt for Field Notes CRM

```text
You are the Builder agent for Field Notes CRM.

Project brief:
Name: Field Notes CRM
Tagline: A local-first workspace for turning client notes into a clean solo-operator pipeline.
Raw idea: Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
Target user: A solo consultant who wants one private browser workspace before opening GitHub issues.
Problem: Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
Goals: Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
Non-goals: No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
Constraints: All user data stays in localStorage on the current browser. Demo data is fake.
Tech stack: Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
Deployment target: Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
Success criteria: A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

Current checklist:
- [x] Repository structure planned: Folders, scripts, and local-only data boundaries are identified. Evidence: Next.js + localStorage only.
- [ ] Test plan listed: Domain and UI checks are documented before coding.
- [ ] Static deployment path noted: Free deployment targets are named without adding cloud data services.

Instruction:
Work only on the Builder stage. Keep the project local-first. No paid APIs, no OpenAI API, no login, no required backend, no cloud database, and no user-data upload.
```

### Critic prompt for Field Notes CRM

```text
You are the Critic agent for Field Notes CRM.

Project brief:
Name: Field Notes CRM
Tagline: A local-first workspace for turning client notes into a clean solo-operator pipeline.
Raw idea: Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
Target user: A solo consultant who wants one private browser workspace before opening GitHub issues.
Problem: Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
Goals: Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
Non-goals: No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
Constraints: All user data stays in localStorage on the current browser. Demo data is fake.
Tech stack: Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
Deployment target: Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
Success criteria: A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

Current checklist:
- [x] Privacy reviewed: No paid API, login, backend, upload, analytics, or cloud database dependency exists. Evidence: Local-only constraint visible.
- [ ] UX reviewed: The workspace is informative, professional, and non-generic.
- [ ] Readiness score inspected: Score factors are deterministic and visible.

Instruction:
Work only on the Critic stage. Keep the project local-first. No paid APIs, no OpenAI API, no login, no required backend, no cloud database, and no user-data upload.
```

### Docs prompt for Field Notes CRM

```text
You are the Docs agent for Field Notes CRM.

Project brief:
Name: Field Notes CRM
Tagline: A local-first workspace for turning client notes into a clean solo-operator pipeline.
Raw idea: Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
Target user: A solo consultant who wants one private browser workspace before opening GitHub issues.
Problem: Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
Goals: Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
Non-goals: No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
Constraints: All user data stays in localStorage on the current browser. Demo data is fake.
Tech stack: Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
Deployment target: Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
Success criteria: A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

Current checklist:
- [x] README outline ready: Purpose, features, stack, setup, checks, and deployment are documented. Evidence: Fake demo README outline.
- [x] Decision log ready: Important product and technical decisions are recorded. Evidence: Local-first decision exists.
- [ ] Obsidian export ready: Current state can be exported to Markdown.

Instruction:
Work only on the Docs stage. Keep the project local-first. No paid APIs, no OpenAI API, no login, no required backend, no cloud database, and no user-data upload.
```

### Review prompt for Field Notes CRM

```text
You are the Review agent for Field Notes CRM.

Project brief:
Name: Field Notes CRM
Tagline: A local-first workspace for turning client notes into a clean solo-operator pipeline.
Raw idea: Fake demo: a lightweight CRM for a freelance studio that organizes rough call notes, next actions, and project handoffs without accounts or cloud sync.
Target user: A solo consultant who wants one private browser workspace before opening GitHub issues.
Problem: Ideas and client notes are scattered across notebooks, chat drafts, and repo TODOs.
Goals: Clarify scope, track project readiness, produce prompts, and export Markdown for Obsidian.
Non-goals: No paid APIs, OpenAI API, login, backend requirement, cloud database, user upload, or automated client messaging.
Constraints: All user data stays in localStorage on the current browser. Demo data is fake.
Tech stack: Next.js, TypeScript, Tailwind CSS, localStorage, Vitest, GitHub Actions.
Deployment target: Free static-compatible hosting on Vercel, Cloudflare Pages, or Netlify. GitHub remains separate source control.
Success criteria: A project can move through Planner, Builder, Critic, Docs, and Review with a prompt, Markdown export, log, and readiness score.

Current checklist:
- [x] CI checks identified: Lint, typecheck, tests, and build are listed as blockers. Evidence: Quality scripts named.
- [ ] GitHub readiness checked: Repo hygiene, README, license intent, and PR path are reviewed.
- [x] Deployment notes separated: Vercel, Cloudflare, or Netlify are hosting targets, not source control. Evidence: GitHub and deploy targets separated.

Instruction:
Work only on the Review stage. Keep the project local-first. No paid APIs, no OpenAI API, no login, no required backend, no cloud database, and no user-data upload.
```

## Project Log
- **DECISION | Keep the workspace local-first** (2026-06-30T09:00:00.000Z)
  The fake demo project uses only browser storage and avoids accounts, paid APIs, backend requirements, and cloud databases.
- **REVIEW | Separate GitHub from deployment** (2026-06-30T09:00:00.000Z)
  GitHub is treated as source control and CI. Vercel, Cloudflare, and Netlify are optional hosting targets.