Instruction file imported from aamirbohra72/Follett-ReportModule (.github/instructions/cip-task-workflow.instructions.md). Copyright stays with the author.

CIP Task Workflow — Copilot Instructions

Wiki is the Single Source of Truth

wiki/ holds all project knowledge. Always consult it before acting.

Full workflow rules: wiki/tasks/README.md

Before Starting Any Implementation

1. Check wiki/tasks/ for a task file matching the work about to be done
2. If no task file exists → create one in todo/ first
3. Create a new git branch named after the task: git checkout -b task/TASK-NNN-kebab-case-title
4. Move the task file to in-progress/ and record the branch name in the Notes section
5. Read the relevant wiki/architecture/ doc to understand design intent

After Completing Work

1. Move the task file from in-progress/ to done/
2. Add completion date and PR/commit reference in the Notes section
3. Update the Status Snapshot table in wiki/tasks/README.md

Task File Rules

• Naming: TASK-NNN-kebab-case-title.md — sequential numbers, never reused
• One task = one logical unit of work (not one file, not one PR)
• Required sections: "What" + at least one Acceptance Criterion
• Never edit done/ files except to correct factual errors
• Files are moved, not copied — the filename stays the same throughout its lifecycle

Hard Rules — Always Follow

• DO NOT create new markdown files to document or summarize completed changes unless the user explicitly asks
• DO NOT skip the task check step before implementing — always verify task state first
• DO NOT add architecture insights as task files — update wiki/architecture/ directly
• DO NOT copy task files across folders — move them