This is the FSS Business KB vault (D:\FSS\KB\Business\). There is a separate MBR KB vault at D:\FSS\KB\MBR\. Never write files from one vault into the other. Each has its own git repo and task system.

KB Task & Note Management — Claude Code Instructions

Full guide: D:\FSS\KB\Business\03_Processes\Simple Markdown Task Management\SMTM_System.md

Location

WSL Path: /mnt/d/FSS/KB/Business/_WorkingOn/ Windows Path: D:\FSS\KB\Business\_WorkingOn\

Folder Structure

_WorkingOn/
├── Tasks/
│   ├── _tmp.md                  # Scratch file for quick/temporary tasks
│   ├── Tasks-Template.md        # SSoT template for task files
│   └── YYYY-MM-DD_Name.md       # Named task files (active until complete)
├── Projects/[name]/
│   ├── STATUS.md                # Phase tracking + feedback (AI reads first)
│   ├── SPEC.md                  # Requirements (no date prefix, stays current)
│   ├── PLAN.md                  # Approach + phases (stays current)
│   ├── TASKS.md                 # Active task checklist (stays current)
│   ├── LESSONS.md               # Insights captured during project
│   └── logs/                    # YYYY-MM-DD_Description.md (session logs)
└── Research/[topic]/

Session Start (MANDATORY)

1. Read Tasks/_tmp.md
2. If working on a project: read Projects/[name]/STATUS.md
3. Check ## Feedback in STATUS.md — act on it before proceeding

Task Lifecycle

Quick task (no log needed): Add checkbox to Tasks/_tmp.md — tick when done, fill in Claude Response section, never delete history.

Substantive task (needs context across sessions):

• Create Tasks/YYYY-MM-DD_Task-Name.md from Tasks-Template.md
• Single file for entire lifecycle — append Claude Response / Talbot Response to END, never delete history
• AI always appends ## Talbot Response + --- after its section
• Use /task-continue [filename] to continue; /task-complete [filename] to close

Project Lifecycle

Session end:

1. Tick completed checkboxes in STATUS.md, update Last Updated date
2. Write log: Projects/[name]/logs/YYYY-MM-DD_Description.md
3. Add blank ## Feedback section to log
4. Update Tasks/_tmp.md

Log Naming

YYYY-MM-DD_Description.md — no TYPE prefix on completed logs.

Git Commits (MANDATORY)

After any session that adds or modifies KB content, suggest a git commit. Do not wait for the user to ask. Automatically propose the commit with a meaningful message covering what changed. The KB repo is /mnt/d/FSS/KB/Business/.

---

Closing Communication (MANDATORY)

After any task that produces a log or task file, the final message must include both paths:

📄 Task/log file:
  WSL:     /mnt/d/FSS/KB/Business/_WorkingOn/...
  Windows: D:\FSS\KB\Business\_WorkingOn\...

Skills

Skill	What it does
/task-start [file]	First session on a task: read, execute, append first Claude Response
/task-continue [file]	Process latest Talbot Response in task file, append Claude Response
/task-complete [file]	Close task: LESSONS.md candidates, purge, log/delete, commit offer
/session-close	Project session end: write log, update STATUS.md, update _tmp.md
/project-start [name]	Create project folder with STATUS.md and initial structure