planflow-ai 1.1.7 → 1.1.9

package/.claude/resources/core/project-tasklist.md

@@ -11,6 +11,10 @@ A persistent project todo list that tracks work items across sessions. The taskl
 
 ## Behavior
 
+### CRITICAL: All Tasks MUST Be Written to Disk
+
+**NEVER keep tasks in-memory only.** Every task addition, status change, or update MUST be written to `flow/tasklist.md` immediately using the Edit or Write tool. If a user asks to add tasks to the tasklist, you MUST edit the file — not just acknowledge the tasks in conversation. The tasklist is a **file on disk**, not a conversation artifact.
+
 ### On Session Start
 
 1. Check if `flow/tasklist.md` exists
@@ -27,6 +31,7 @@ A persistent project todo list that tracks work items across sessions. The taskl
 - When a task is completed (skill finishes successfully), move it to **Done** with the completion date
 - When new work items are discovered during execution, add them to **To Do**
 - Update `flow/tasklist.md` in real-time as work progresses
+- **EVERY update MUST be persisted to `flow/tasklist.md` via Edit/Write tool — no exceptions**
 
 ### Task Format
 
@@ -221,3 +226,4 @@ When a task is completed:
 6. **Always update**: Every command MUST update the tasklist — this is not optional
 7. **Add vs Execute**: When the user says "add to tasklist" or "add a task for X", ONLY add it to **To Do**. Do NOT start working on it. Only execute when the user explicitly says "do this", "implement this", "work on X", or invokes a command.
 8. **Tasklist is a backlog**: The tasklist is a planning tool, not an execution trigger. Adding a task is separate from executing it.
+9. **Persist to disk — ALWAYS**: Every task addition or status change MUST be written to `flow/tasklist.md` using Edit or Write. NEVER keep tasks only in conversation memory. If you added tasks but did not call Edit/Write on `flow/tasklist.md`, you have a bug — fix it immediately.

package/README.md

@@ -7,7 +7,7 @@ Works with **Claude Code**, **Cursor**, **OpenClaw**, and **Codex CLI**.
 ## Quick Start
 
 ```bash
-npx plan-flow init
+npx planflow-ai init
 ```
 
 This interactive command installs plan-flow into your project for your chosen platform(s).
@@ -17,7 +17,7 @@ This interactive command installs plan-flow into your project for your chosen pl
 ### Claude Code
 
 ```bash
-npx plan-flow init --claude
+npx planflow-ai init --claude
 ```
 
 Installs slash commands (`.claude/commands/`), core rules (`.claude/rules/`), and reference docs (`.claude/resources/`) into your project. Creates or updates your `CLAUDE.md` with plan-flow instructions.
@@ -25,15 +25,15 @@ Installs slash commands (`.claude/commands/`), core rules (`.claude/rules/`), an
 ### Cursor
 
 ```bash
-npx plan-flow init --cursor
+npx planflow-ai init --cursor
 ```
 
-Copies Cursor-compatible rules (`rules/*.mdc`) into your project.
+Copies Cursor-compatible commands (`.cursor/commands/`) into your project.
 
 ### OpenClaw
 
 ```bash
-npx plan-flow init --openclaw
+npx planflow-ai init --openclaw
 ```
 
 Copies skill manifests to `skills/plan-flow/` in your project.
@@ -41,7 +41,7 @@ Copies skill manifests to `skills/plan-flow/` in your project.
 ### Codex CLI
 
 ```bash
-npx plan-flow init --codex
+npx planflow-ai init --codex
 ```
 
 Copies skills to `.agents/skills/plan-flow/` and creates or updates your `AGENTS.md` with plan-flow instructions.
@@ -49,7 +49,7 @@ Copies skills to `.agents/skills/plan-flow/` and creates or updates your `AGENTS
 ### All Platforms
 
 ```bash
-npx plan-flow init --all
+npx planflow-ai init --all
 ```
 
 Installs for Claude Code, Cursor, OpenClaw, and Codex CLI simultaneously.
@@ -66,28 +66,6 @@ Installs for Claude Code, Cursor, OpenClaw, and Codex CLI simultaneously.
 | `--force` | Overwrite existing files |
 | `--target <dir>` | Target directory (defaults to current) |
 
-## Manual Installation
-
-### Claude Code (Manual)
-
-1. Copy `.claude/commands/*.md` to your project's `.claude/commands/`
-2. Copy `.claude/rules/` to your project's `.claude/rules/`
-3. Copy `.claude/resources/` to your project's `.claude/resources/`
-4. Add the plan-flow section from `templates/shared/CLAUDE.md.template` to your `CLAUDE.md`
-
-### Cursor (Manual)
-
-Copy `rules/` to your project's `rules/`
-
-### OpenClaw (Manual)
-
-Copy `skills/plan-flow/` to your project's `skills/plan-flow/`
-
-### Codex CLI (Manual)
-
-1. Copy `skills/plan-flow/` to your project's `.agents/skills/plan-flow/`
-2. Add the plan-flow section from `templates/shared/AGENTS.md.template` to your `AGENTS.md`
-
 ## Commands
 
 | Command | Description |
@@ -100,7 +78,7 @@ Copy `skills/plan-flow/` to your project's `skills/plan-flow/`
 | `/review-code` | Review local uncommitted changes |
 | `/review-pr` | Review a Pull Request |
 | `/write-tests` | Generate tests for coverage target |
-| `/flow` | Toggle autopilot mode on/off |
+| `/flow` | Configure plan-flow settings (autopilot, git control, runtime options) |
 | `/brain` | Capture meeting notes, ideas, brainstorms |
 | `/learn` | Extract reusable patterns or learn a topic step-by-step |
 | `/pattern-validate` | Scan and index global brain patterns |
@@ -120,7 +98,7 @@ Copy `skills/plan-flow/` to your project's `skills/plan-flow/`
 
 ### Autopilot Mode
 
-Enable autopilot with `/flow -enable` and the full workflow runs automatically for feature requests:
+Enable autopilot with `/flow autopilot=true` and the full workflow runs automatically for feature requests:
 
 ```
 You: "Add dark mode support"
@@ -135,17 +113,101 @@ You: "Add dark mode support"
 
 Autopilot classifies every input and only triggers the full flow for feature requests (complexity 3+). Questions, trivial tasks, and slash commands are handled normally.
 
-| Usage | Description |
-|-------|-------------|
-| `/flow -enable` | Enable autopilot mode |
-| `/flow -disable` | Disable autopilot mode |
-| `/flow -status` | Check current state |
-
 **Mandatory checkpoints** — even in autopilot, the flow always pauses for:
 - **Discovery Q&A**: You answer requirements questions
 - **Plan approval**: You review and approve the plan before execution
 
-State is persisted in `flow/.autopilot` (survives session restarts).
+## Flow Configuration (`/flow`)
+
+The `/flow` command is the central configuration hub. All settings use `key=value` syntax and persist in `flow/.flowconfig` (YAML).
+
+| Setting | Values | Default | Description |
+|---------|--------|---------|-------------|
+| `autopilot` | `true/false` | `false` | Enable/disable autopilot mode |
+| `commit` | `true/false` | `false` | Auto-commit after each completed phase |
+| `push` | `true/false` | `false` | Auto-push after all phases + build/test pass |
+| `branch` | any string | current branch | Target branch for git operations |
+
+### Examples
+
+```bash
+/flow autopilot=true                    # Enable autopilot
+/flow commit=true push=true             # Enable git control (works without autopilot)
+/flow autopilot=true commit=true        # Enable both
+/flow branch=development                # Set target branch
+/flow -status                           # Show current config
+/flow -reset                            # Reset everything
+
+# Shorthand: text without key=value enables autopilot and starts flow
+/flow add dark mode support             # autopilot=true + start discovery
+/flow commit=true add user auth         # autopilot=true + git + start discovery
+```
+
+### Git Control
+
+When `commit=true`, plan-flow auto-commits after each completed execution phase:
+
+```
+Phase 1: Setup types → git commit "Phase 1: Setup types — user-auth"
+Phase 2: API endpoints → git commit "Phase 2: API endpoints — user-auth"
+Phase 3: Tests → git commit "Phase 3: Tests — user-auth"
+Build + Test pass → git commit "Complete: user-auth — all phases done"
+                  → git push origin development (if push=true)
+```
+
+Git control works independently of autopilot — you can use `commit=true` with manual `/execute-plan` runs.
+
+## Project Tasklist
+
+Each project has a `flow/tasklist.md` that tracks work items across sessions. On session start, active tasks are summarized and you can pick one to work on.
+
+Every command automatically updates the tasklist:
+- On start: adds the task to **In Progress**
+- On complete: moves it to **Done** with the date
+- Next step: adds the logical follow-up to **To Do**
+
+### Scheduled Tasks
+
+Tasks can be scheduled for later execution by linking them to the heartbeat daemon:
+
+```
+/flow add to tasklist: implement feature X and execute in 1 hour
+```
+
+This creates a tasklist entry linked to a heartbeat one-shot task via `[[]]` references. Both files cross-reference each other for Obsidian navigation.
+
+## Heartbeat (Scheduled Automation)
+
+The heartbeat daemon is a background process that executes scheduled tasks defined in `flow/heartbeat.md`.
+
+### Schedule Syntax
+
+| Syntax | Example |
+|--------|---------|
+| `daily at {HH:MM AM/PM}` | `daily at 10:00 PM` |
+| `every {N} hours` | `every 6 hours` |
+| `every {N} minutes` | `every 30 minutes` |
+| `weekly on {day} at {HH:MM}` | `weekly on Monday at 9:00 AM` |
+| `in {N} hours` | `in 2 hours` (one-shot) |
+| `in {N} minutes` | `in 30 minutes` (one-shot) |
+
+### Daemon Management
+
+```bash
+npx planflow-ai heartbeat start    # Start the daemon
+npx planflow-ai heartbeat stop     # Stop the daemon
+npx planflow-ai heartbeat status   # Show daemon status
+```
+
+The daemon **auto-starts** during `planflow-ai init` if `flow/heartbeat.md` exists.
+
+### One-Shot Tasks
+
+Tasks with `in {N} hours/minutes` schedules run once and auto-disable after execution. These are used for scheduled tasklist items.
+
+### Retry on Active Session
+
+If a task fails because a Claude Code session is already active, the daemon retries up to 5 times at 60-second intervals instead of failing permanently.
 
 ## Complexity Scoring
 
@@ -177,11 +239,13 @@ flow/
 ├── resources/         # Valuable artifacts captured during skill execution
 ├── reviewed-code/     # Code review documents
 ├── reviewed-pr/       # PR review documents
-├── tasklist.md        # Project task list (loaded on session start)
+├── tasklist.md        # Project task list (updated in real-time during execution)
 ├── memory.md          # Persistent artifact tracker (completed work)
 ├── heartbeat.md       # Scheduled task definitions for the heartbeat daemon
 ├── log.md             # Heartbeat event log
-└── ledger.md          # Persistent project learning journal
+├── ledger.md          # Persistent project learning journal
+├── .flowconfig        # Central config file (autopilot, git control, settings)
+└── .gitcontrol        # Git control settings (backward compat)
 ```
 
 ## Session Start Behaviors
@@ -192,30 +256,23 @@ When a session starts, plan-flow automatically loads context from your project:
 - **Memory** (`flow/memory.md`) — Loads the last 7 days of completed work so context is never lost
 - **Brain** (`flow/brain/index.md`) — Internalizes active features and recent error patterns
 - **Ledger** (`flow/ledger.md`) — Internalizes project-specific lessons learned
+- **Autopilot** (`flow/.flowconfig`) — If `autopilot: true`, activates automatic workflow orchestration
 
 ## Intelligent Learn Skill
 
 The `/learn` skill supports step-by-step teaching. When you run `/learn about <topic>`, it creates a structured curriculum stored as a brain `.md` file. Each step requires your confirmation before progressing, and confirmed steps become learned patterns.
 
-## Project Tasklist
-
-Each project can have a `flow/tasklist.md` with pending tasks. On session start, the tasklist is loaded and you're asked if you want to pick a task. Completed tasks are tracked in project memory.
+Commands also recommend `/learn` automatically when:
+- New dependencies are added during execution
+- Non-trivial errors are resolved (3+ attempts)
+- The user corrects the approach
+- A new technology or pattern is introduced
 
-## Project Memory
+## Central Obsidian Vault
 
-`flow/memory.md` tracks everything completed across sessions. Each entry includes a timestamp, project link, artifact type, file path, and a short summary (max 6 lines). The last 7 days of memory are loaded on every session start, ensuring plan-flow never loses knowledge.
-
-## Heartbeat (Scheduled Automation)
-
-The `flow/heartbeat.md` file works as a cronjob system. Define scheduled tasks and the heartbeat daemon will execute them automatically:
-
-```
-do
-  daily at 10:00 PM - research about topic X, create md files and add to brain
-  daily at 11:00 AM - using flow --enabled, create feature Y, execute, and push to repo
-```
+All projects are linked into a central Obsidian vault at `~/plan-flow/brain/`. Each `planflow-ai init` creates a project directory in the vault with symlinks for brain subdirectories and the tasklist. A global tasklist at `~/plan-flow/brain/tasklist.md` aggregates task counts across all projects.
 
-Manage the daemon with `/heartbeat start`, `/heartbeat stop`, and `/heartbeat status`.
+Open `~/plan-flow/brain/` as an Obsidian vault to browse all projects in one graph.
 
 ## Requirements
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "planflow-ai",
-  "version": "1.1.7",
+  "version": "1.1.9",
   "description": "Structured AI-assisted development workflows for discovery, planning, execution, code reviews, and testing",
   "type": "module",
   "main": "dist/cli/index.js",

package/rules/core/_index.mdc

@@ -63,6 +63,14 @@ Core rules define the foundational coding standards that apply across the entire
 | COR-BR-2 | File templates (feature, error, decision, session) and naming conventions | brain-capture.mdc | 52-100 |
 | COR-BR-3 | Index management (caps, rotation) and brain vs ledger comparison | brain-capture.mdc | 102-140 |
 
+### Project Tasklist (`project-tasklist.mdc`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-TL-1 | Tasklist disk persistence rules and session behavior | project-tasklist.mdc | 10-50 |
+| COR-TL-2 | Command integration and update rules | project-tasklist.mdc | 52-80 |
+| COR-TL-3 | Task management rules (persist to disk, no duplicates, add vs execute) | project-tasklist.mdc | 82-100 |
+
 ### Resource Capture (`resource-capture.mdc`)
 
 | Code | Description | Source | Lines |
@@ -93,6 +101,9 @@ Core rules define the foundational coding standards that apply across the entire
 | COR-AM-1 | Need to understand input classification for autopilot |
 | COR-AM-2 | Need autopilot flow execution steps |
 | COR-AM-3 | Need mandatory checkpoint and override rules |
+| COR-TL-1 | Need tasklist disk persistence and session behavior |
+| COR-TL-2 | Need tasklist command integration rules |
+| COR-TL-3 | Need tasklist management rules |
 | COR-RC-1 | Need resource capture behavior and criteria |
 | COR-RC-2 | Need resource file format and naming conventions |
 
@@ -130,4 +141,5 @@ Core rules define the foundational coding standards that apply across the entire
 - `brain-capture.mdc` has `alwaysApply: false` - loaded when `flow/brain/index.md` exists or when brain-capture blocks need processing
 - `complexity-scoring.mdc` has `alwaysApply: false` - loaded on-demand when needed for planning
 - `autopilot-mode.mdc` has `alwaysApply: false` - loaded when autopilot mode is active (`flow/.autopilot` exists)
+- `project-tasklist.mdc` has `alwaysApply: false` - loaded when `flow/tasklist.md` exists or when tasks are being managed
 - `resource-capture.mdc` has `alwaysApply: false` - loaded during skill execution to watch for valuable reference materials

package/rules/core/project-tasklist.mdc

@@ -0,0 +1,90 @@
+---
+description: "Project tasklist persistence - ensures tasks are always written to flow/tasklist.md on disk. Include when working with tasks, backlogs, or when flow/tasklist.md exists."
+alwaysApply: false
+---
+
+# Project Tasklist
+
+## Purpose
+
+A persistent project todo list that tracks work items across sessions. The tasklist is loaded at session start to provide continuity and help users pick up where they left off.
+
+**Location**: `flow/tasklist.md`
+
+---
+
+## CRITICAL: All Tasks MUST Be Written to Disk
+
+**NEVER keep tasks in-memory only.** Every task addition, status change, or update MUST be written to `flow/tasklist.md` immediately. If a user asks to add tasks to the tasklist, you MUST edit the file — not just acknowledge the tasks in conversation. The tasklist is a **file on disk**, not a conversation artifact.
+
+---
+
+## Behavior
+
+### On Session Start
+
+1. Check if `flow/tasklist.md` exists
+2. If it exists: read it silently and internalize the content
+3. Present a brief summary of active tasks:
+   - Count of **In Progress** items
+   - Count of **To Do** items
+4. Ask the user if they want to pick a task from the list
+5. Do NOT read the full tasklist aloud — just summarize counts and top items
+
+### During Work
+
+- When a task is picked by the user, mark it as **In Progress** in `flow/tasklist.md`
+- When a task is completed (skill finishes successfully), move it to **Done** with the completion date
+- When new work items are discovered during execution, add them to **To Do**
+- Update `flow/tasklist.md` in real-time as work progresses
+- **EVERY update MUST be persisted to `flow/tasklist.md` — no exceptions**
+
+### Task Format
+
+```markdown
+## In Progress
+
+- [ ] Task description — started {YYYY-MM-DD}
+
+## To Do
+
+- [ ] Task description
+
+## Done
+
+- [x] Task description — completed {YYYY-MM-DD}
+```
+
+---
+
+## Command Integration
+
+Every plan-flow command MUST update the tasklist at specific points:
+
+| Command | On Start | On Complete | Next Task Added |
+|---------|----------|-------------|-----------------|
+| `/discovery` | Add "Discovery: {feature}" → In Progress | Move to Done | Add "Create plan for {feature}" → To Do |
+| `/create-plan` | Add "Plan: {feature}" → In Progress | Move to Done | Add "Execute plan for {feature}" → To Do |
+| `/execute-plan` | Add "Execute: {feature}" → In Progress | Move to Done | Add "Review code for {feature}" → To Do |
+| `/review-code` | Add "Review: {scope}" → In Progress | Move to Done | — |
+| `/review-pr` | Add "Review PR: #{number}" → In Progress | Move to Done | — |
+| `/write-tests` | Add "Tests: {scope}" → In Progress | Move to Done | — |
+
+### Update Rules
+
+1. **On command start**: Check if the task already exists. If yes, move it to In Progress. If no, add it.
+2. **On command complete**: Move from In Progress to Done with today's date.
+3. **Next step task**: Add the logical next step to To Do.
+4. **User requests**: When the user asks to add tasks outside a command, add them to **To Do** in `flow/tasklist.md` immediately.
+
+---
+
+## Rules
+
+1. **Summarize, don't dump**: On session start, show counts and top 3 items, not the full list
+2. **Real-time updates**: Update tasklist immediately when status changes, don't batch
+3. **No duplicates**: Before adding a task, check if it already exists (check all sections)
+4. **User-driven**: Only pick/execute tasks when the user explicitly asks to
+5. **Add vs Execute**: "Add to tasklist" = add to To Do. "Do this" = execute. They are separate actions.
+6. **Always update**: Every command MUST update the tasklist — this is not optional
+7. **Persist to disk — ALWAYS**: Every task addition or status change MUST be written to `flow/tasklist.md`. NEVER keep tasks only in conversation memory. If you added tasks but did not write to the file, you have a bug — fix it immediately.

package/rules/skills/create-plan-skill.mdc

@@ -269,3 +269,11 @@ Before completing the plan, verify:
 | `flow/plans/`                                  | Output folder for plan documents |
 | `flow/discovery/`                              | Input discovery documents        |
 
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Plan: {feature}" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Plan: {feature}" to **Done** with today's date
+3. **Next step**: Add "Execute plan for {feature}" to **To Do**
+

package/rules/skills/discovery-skill.mdc

@@ -296,3 +296,11 @@ Before completing discovery, verify:
 | `.cursor/rules/tools/interactive-questions-tool.mdc` | Interactive Questions UI workflow |
 | `flow/discovery/`                                 | Output folder for discovery docs  |
 
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Discovery: {feature}" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Discovery: {feature}" to **Done** with today's date
+3. **Next step**: Add "Create plan for {feature}" to **To Do**
+

package/rules/skills/execute-plan-skill.mdc

@@ -396,3 +396,11 @@ During this skill's execution, watch for valuable reference materials worth pres
 At natural break points, if you encounter information that could be useful for future development (API specs, architecture notes, config references, domain knowledge, etc.), ask the user: "I found something that could be useful for future reference: _{brief description}_. Should I save it to `flow/resources/`?"
 
 Only save if the user approves. Do not re-ask if declined.
+
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Execute: {feature}" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Execute: {feature}" to **Done** with today's date
+3. **Next step**: Add "Review code for {feature}" to **To Do**

package/rules/skills/review-code-skill.mdc

@@ -307,3 +307,10 @@ After running this command:
 
 > The goal is not just to review current changes, but to **improve the codebase patterns over time** by documenting good patterns and preventing anti-patterns from spreading.
 
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Review: {scope}" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Review: {scope}" to **Done** with today's date
+

package/rules/skills/review-pr-skill.mdc

@@ -497,3 +497,10 @@ Authentication is handled by the **[PR Authentication Tool](../tools/auth-pr-too
 - Error handling
 - Security notes
 
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Review PR: #{number}" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Review PR: #{number}" to **Done** with today's date
+

package/rules/skills/write-tests-skill.mdc

@@ -302,3 +302,10 @@ During this skill's execution, watch for valuable reference materials worth pres
 At natural break points, if you encounter information that could be useful for future development (API specs, architecture notes, config references, domain knowledge, etc.), ask the user: "I found something that could be useful for future reference: _{brief description}_. Should I save it to `flow/resources/`?"
 
 Only save if the user approves. Do not re-ask if declined.
+
+## Tasklist Updates
+
+Update `flow/tasklist.md` at these points (you MUST write to the file, not keep in memory):
+
+1. **On start**: Add "Tests: {scope} ({target}%)" to **In Progress** (or move it from To Do if it already exists)
+2. **On complete**: Move "Tests: {scope}" to **Done** with today's date

package/skills/plan-flow/SKILL.md

@@ -33,6 +33,7 @@ A comprehensive skill set for AI-assisted software development with structured w
 |---------|-------------|
 | Project Ledger | Persistent learning journal at `flow/ledger.md` - silently captures mistakes, corrections, and project-specific knowledge across sessions |
 | Project Brain | Automatic knowledge capture at `flow/brain/` - records features, errors, decisions, and session logs with Obsidian-compatible `[[wiki-links]]` |
+| Project Tasklist | Persistent todo list at `flow/tasklist.md` — **MUST be written to disk**, never kept in-memory only. Every task addition or status change must edit the file immediately. |
 | Resource Capture | During any skill execution, watches for valuable reference materials (API specs, architecture notes, domain knowledge) and asks user before saving to `flow/resources/` |
 
 ## Recommended Workflow
@@ -102,6 +103,7 @@ flow/
 3. **Tests Last**: Tests are always the last phase of any implementation plan.
 4. **Build at End Only**: Run build verification only after ALL phases complete.
 5. **Archive When Done**: Move completed discovery and plans to `flow/archive/`.
+6. **Tasklist is a file, not memory**: When adding, moving, or completing tasks, you MUST write changes to `flow/tasklist.md`. NEVER keep tasks only in conversation memory.
 
 ## Configuration
 

package/templates/shared/AGENTS.md.template

@@ -31,12 +31,23 @@ The Project Ledger (`flow/ledger.md`) is always active. It silently captures pro
 
 The Project Brain (`flow/brain/`) automatically captures features, errors, decisions, and session logs during skill execution. If `flow/brain/index.md` exists, read it silently at session start. Uses Obsidian-compatible `[[wiki-links]]` for cross-referencing.
 
+## Project Tasklist
+
+The Project Tasklist (`flow/tasklist.md`) tracks work items across sessions. If it exists, read it silently at session start and present a brief summary of active task counts.
+
+**CRITICAL**: When adding, moving, or completing tasks, you MUST write changes to `flow/tasklist.md` on disk. NEVER keep tasks only in conversation memory. If the user says "add to tasklist", read the file, then edit it. The tasklist is a **file on disk**, not a conversation artifact.
+
+## Project Memory
+
+The Project Memory (`flow/memory.md`) tracks completed skill executions. If it exists, read it silently at session start and internalize the last 7 days of completed work.
+
 ## Critical Rules
 
 1. **No Auto-Chaining**: Never auto-invoke the next command. Wait for user. **Exception**: When autopilot mode is ON (`flow/.autopilot` exists), commands auto-chain per the autopilot flow skill.
 2. **Discovery First**: Recommend `/discovery-plan` before `/create-plan` for new features.
 3. **Tests Last**: Tests are always the last phase of any implementation plan.
 4. **Build at End Only**: Run `npm run build` only after ALL phases complete.
+5. **Tasklist is a file, not memory**: When adding, moving, or completing tasks, you MUST write changes to `flow/tasklist.md`. NEVER keep tasks only in conversation memory.
 
 ## Flow Directory Structure
 
@@ -53,7 +64,13 @@ flow/
 ├── references/        # Reference materials
 ├── reviewed-code/     # Code review documents
 ├── reviewed-pr/       # PR review documents
-└── ledger.md          # Persistent project learning journal
+├── tasklist.md        # Project todo list (updated in real-time during execution)
+├── memory.md          # Persistent artifact tracker (completed skill executions)
+├── heartbeat.md       # Scheduled task definitions for the heartbeat daemon
+├── log.md             # Heartbeat log of important events
+├── ledger.md          # Persistent project learning journal
+├── .flowconfig        # Central config file (autopilot, git control, settings)
+└── .gitcontrol        # Git control settings — backward compat (prefer .flowconfig)
 ```
 
 ## Complexity Scoring

package/templates/shared/CLAUDE.md.template

@@ -27,7 +27,9 @@
 
 - **Project Ledger**: If `flow/ledger.md` exists, read it silently and internalize learnings. Update it when you learn project-specific lessons. See `.claude/resources/core/project-ledger.md` for full rules.
 - **Project Brain**: If `flow/brain/index.md` exists, read it silently and internalize active features and recent errors. See `.claude/resources/core/brain-capture.md` for full rules.
-- **Autopilot Mode**: If `flow/.autopilot` exists, read `.claude/resources/core/autopilot-mode.md` and follow its workflow for every user input.
+- **Project Tasklist**: If `flow/tasklist.md` exists, read it silently and present a brief summary of active tasks. See `.claude/resources/core/project-tasklist.md` for full rules.
+- **Project Memory**: If `flow/memory.md` exists, read it silently and internalize the last 7 days of completed work. See `.claude/resources/core/project-memory.md` for full rules.
+- **Autopilot Mode**: If `flow/.flowconfig` has `autopilot: true` (or `flow/.autopilot` exists for backward compat), read `.claude/resources/core/autopilot-mode.md` and follow its workflow for every user input.
 
 ## Critical Rules
 
@@ -35,6 +37,7 @@
 2. **Discovery First**: `/discovery-plan` is **required** before `/create-plan`. Plans cannot be created without a discovery document. No exceptions.
 3. **Tests Last**: Tests are always the last phase of any implementation plan.
 4. **Build at End Only**: Run `npm run build` only after ALL phases complete.
+5. **Tasklist is a file, not memory**: When adding, moving, or completing tasks, you MUST use the Edit tool to write changes to `flow/tasklist.md`. NEVER keep tasks only in conversation memory. If the user says "add to tasklist", read `flow/tasklist.md`, then Edit it. See `.claude/resources/core/project-tasklist.md` for full rules.
 
 ## Flow Directory Structure
 
@@ -51,7 +54,13 @@ flow/
 ├── references/        # Reference materials
 ├── reviewed-code/     # Code review documents
 ├── reviewed-pr/       # PR review documents
-└── ledger.md          # Persistent project learning journal
+├── tasklist.md        # Project todo list (updated in real-time during execution)
+├── memory.md          # Persistent artifact tracker (completed skill executions)
+├── heartbeat.md       # Scheduled task definitions for the heartbeat daemon
+├── log.md             # Heartbeat log of important events
+├── ledger.md          # Persistent project learning journal
+├── .flowconfig        # Central config file (autopilot, git control, settings)
+└── .gitcontrol        # Git control settings — backward compat (prefer .flowconfig)
 ```
 
 ## Central Vault