From 890a63ef5fa7cac27983e9b9569d173b790670fc Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 01:47:19 +0000 Subject: [PATCH 1/7] Phase 1: Consolidate workflow guidance into Orchestration Skill MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Add YAML frontmatter to stub files (events-system.md, wordpress-block-patterns.md) - Fix broken path references in README.md (../data → ./data-models) - Replace inline workflow sections in Guidelines.md with Skill references - Create .claude/skills/workflow-orchestration/SKILL.md (3.5KB) Changes consolidate 3 files worth of workflow guidance (prompt/report/task creation) into reusable Skill with decision trees, templates, and step-by-step procedures. Reduces Guidelines.md maintenance burden while preserving accessibility via skill references. Remedies findings F006 (missing frontmatter) and F007 (broken references) from TOA-358 audit. Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .../skills/workflow-orchestration/SKILL.md | 607 ++++++++++++++++++ guidelines/Guidelines.md | 44 +- guidelines/README.md | 4 +- guidelines/events-system.md | 9 + guidelines/wordpress-block-patterns.md | 9 + 5 files changed, 644 insertions(+), 29 deletions(-) create mode 100644 .claude/skills/workflow-orchestration/SKILL.md diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md new file mode 100644 index 00000000..d9886148 --- /dev/null +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -0,0 +1,607 @@ +--- +name: "Workflow Orchestration Skill" +description: "Guides the 4-step audit/prompt/report/task workflow with templates and best practices for ThisOneTimeOnAcidCom." +type: "skill" +category: "workflow" +enabled: true +tags: ["workflow", "audit", "prompt", "report", "task", "orchestration"] +version: "1.0.0" +created: "2026-10-22" +--- + +# Workflow Orchestration Skill + +## Purpose + +Guide teams through the **4-step AI-assisted workflow** used in ThisOneTimeOnAcidCom: + +1. **Create prompt** — Define audit scope and methodology +2. **Run audit** — Execute against codebase and guidelines +3. **Save report** — Document findings with evidence +4. **Extract tasks** — Decompose into actionable checklist + +This skill consolidates guidance from: +- `guidelines/Guidelines.md` § "Default AI Workflow" +- `guidelines/prompt-creation-guidelines.md` +- `guidelines/report-creation-guidelines.md` + +--- + +## When to Use + +Use this skill when: +- ✅ Writing a new audit or investigation prompt +- ✅ Setting up a report structure for findings +- ✅ Creating a task list from audit results +- ✅ Archiving completed work +- ✅ Running multi-step orchestrator audits + +## Workflow Decision Tree + +**Start here:** What are you doing? + +``` +Are you running an audit/investigation? +├─ YES → Continue below +└─ NO → This skill may not apply; check specific domain skills + +Single audit or multi-step orchestrator? +├─ Single audit (one .md file) → Section: Single-File Workflow +├─ Multi-step (orchestrator + sub-prompts) → Section: Orchestrator Workflow +└─ Archiving completed work → Section: Archiving Completed Work +``` + +--- + +## Section 1: Single-File Workflow + +**Use this for:** Simple one-time audits, quick investigations, focused scans + +### Step 1A: Create the Prompt + +**File location:** `/prompts/{topic}.md` + +**Naming convention:** Lowercase, hyphens, descriptive +- ✅ `css-audit.md` +- ✅ `accessibility-violations-audit.md` +- ❌ `CSS Audit.md` (wrong case) +- ❌ `css_audit.md` (underscore instead of hyphen) + +**Required YAML frontmatter:** + +```yaml +--- +title: "Audit Title Here" +filename: "/prompts/{topic}.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +prompt_type: "single-audit" +estimated_duration: "30 minutes" +related_reports: "/reports/{topic}/" +related_tasks: "/tasks/{topic}-tasks.md" +--- +``` + +**Use this template:** Copy from `templates/prompt-frontmatter-single.yml` + +### Step 1B: Define Audit Scope + +**Structure your prompt with:** +- **Objective** — What are you auditing? (1–2 sentences) +- **Scope** — Which files/areas? (bullet list or file patterns) +- **Method** — How will you audit? (step-by-step process) +- **Acceptance criteria** — What counts as "complete"? + +**Example:** +```markdown +--- +title: "CSS Architecture Audit" +# [frontmatter] +--- + +## Objective + +Identify Tailwind utility violations in `/styles/blocks/` and recommend BEM refactoring. + +## Scope + +- All files in `src/styles/blocks/*.css` +- Component JSX files using Tailwind classes +- Exclude: node_modules, dist, archived/ + +## Method + +1. Scan all block CSS files for forbidden patterns +2. List each Tailwind utility found +3. Cross-reference with BEM CSS Compliance Skill +4. Prioritize by frequency and impact + +## Acceptance Criteria + +- [ ] All Tailwind utilities catalogued +- [ ] BEM replacements identified +- [ ] Report saved to `/reports/css-audit/` +``` + +### Step 2A: Run the Audit + +Execute the audit prompt against the codebase. The AI will follow your methodology and document findings. + +### Step 3A: Save the Report + +**File location:** `/reports/{topic}.md` (single file, root of /reports/) + +**Required YAML frontmatter:** + +```yaml +--- +title: "Audit Title Report" +filename: "/reports/{topic}.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +report_type: "audit" +related_prompt: "/prompts/{topic}.md" +related_tasks: "/tasks/{topic}-tasks.md" +status: "complete" +--- +``` + +**Use this template:** Copy from `templates/report-frontmatter-single.yml` + +**Report structure:** +- Executive summary (1 paragraph) +- Findings register (table: ID | Finding | File | Severity | Evidence | Recommendation) +- Recommendations (prioritized by impact) +- Verification steps (how to validate findings) +- Next steps (link to task list) + +### Step 4A: Extract Tasks + +**File location:** `/tasks/{topic}-tasks.md` + +**Required YAML frontmatter:** + +```yaml +--- +title: "Task List: {Topic}" +filename: "/tasks/{topic}-tasks.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +related_prompt: "/prompts/{topic}.md" +related_report: "/reports/{topic}.md" +status: "active" +--- +``` + +**Task list structure:** +- Overview (1–2 sentences on what these tasks accomplish) +- Task checklist (each line is one actionable task) +- Dependencies (if any) +- Estimated completion date + +**Example:** +```markdown +--- +title: "Task List: CSS Architecture Audit" +# [frontmatter] +--- + +## Overview + +Refactor Tailwind utilities to BEM classes across `/styles/blocks/`. 10 tasks, ~4 hours. + +## Tasks + +- [ ] Task 1: Refactor `hero.css` utilities → BEM (hero-hero.css) +- [ ] Task 2: Refactor `blog-card.css` utilities → BEM +- [ ] Task 3: Update component imports (Hero.tsx uses new classes) +- [ ] Task 4: Validate CSS with `/bem-css-compliance` skill +- [ ] Task 5: Run build test to confirm no regressions +- [ ] Task 6: Archive old Tailwind-based block files +- [ ] Task 7: Update Guidelines.md § CSS references +- [ ] Task 8: Commit and push +- [ ] Task 9: Create PR +- [ ] Task 10: Archive completed task list (after PR merge) + +## Dependencies + +- Report: `/reports/css-audit.md` must be complete +- Skill: `/bem-css-compliance` should be available + +## Estimated Completion + +2026-11-01 (4 hours, 2 developers) +``` + +--- + +## Section 2: Orchestrator Workflow + +**Use this for:** Complex audits with multiple stages, different teams, or interdependent investigations + +### Step 1B: Create Orchestrator Folder + +**File location:** `/prompts/{topic}/` + +**Naming convention:** Lowercase, hyphens, descriptive folder + +``` +/prompts/modern-react-migration/ ← folder name +├── 00-ORCHESTRATOR.md ← always named 00-ORCHESTRATOR.md +├── 01-es5-react-audit.md ← sub-prompts numbered 01, 02, 03... +├── 02-tailwind-violations-audit.md +├── 03-css-architecture-alignment.md +└── 04-component-structure-audit.md +``` + +### Step 2B: Create Orchestrator Prompt + +**File location:** `/prompts/{topic}/00-ORCHESTRATOR.md` + +**Required YAML frontmatter:** + +```yaml +--- +title: "Orchestrator: {Topic}" +filename: "/prompts/{topic}/00-ORCHESTRATOR.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +prompt_type: "orchestrator" +estimated_duration: "2 hours" +sub_prompts: ["01-...", "02-...", "03-..."] +related_reports: "/reports/YYYY-MM-DD-{topic}/" +related_tasks: "/tasks/{topic}-tasks.md" +--- +``` + +**Orchestrator structure:** +- Overview (what does this orchestrator accomplish?) +- Sub-prompt list (1–3 sentences per sub-prompt) +- Execution order (which runs first, which depend on others?) +- Consolidation step (how to merge sub-audit findings?) +- Acceptance criteria + +**Example:** +```markdown +--- +title: "Orchestrator: Modern React Migration" +# [frontmatter] +--- + +## Overview + +Audit ThisOneTimeOnAcidCom's React codebase against modern best practices (ES5 bundler compat, +no Tailwind, BEM-only CSS). Four sub-audits run in parallel, then findings consolidate. + +## Sub-Prompts + +### 01-es5-react-audit.md +Verify code conforms to Figma Make bundler restrictions (no optional chaining, nullish +coalescing, import.meta.env, nested ternaries, for...of). + +### 02-tailwind-violations-audit.md +Identify remaining Tailwind utility classes; map to BEM equivalents. + +### 03-css-architecture-alignment.md +Verify all CSS follows semantic BEM; no inline styles; no !important; correct dark mode +selectors. + +### 04-component-structure-audit.md +Review component file organization; confirm protected files aren't modified; validate data +imports from mock/. + +## Execution Order + +**Parallel phase (all run simultaneously):** +- Sub-prompt 01 (ES5 audit) +- Sub-prompt 02 (Tailwind audit) +- Sub-prompt 03 (CSS architecture) +- Sub-prompt 04 (Component structure) + +**Consolidation phase (after all complete):** +- Merge findings into master report +- Prioritize by frequency + impact +- Create unified task list + +## Acceptance Criteria + +- [ ] All 4 sub-audits complete +- [ ] Consolidated report in `/reports/YYYY-MM-DD-modern-react-migration/` +- [ ] Task list extracted to `/tasks/modern-react-migration-tasks.md` +``` + +### Step 3B: Create Sub-Prompts + +**File location:** `/prompts/{topic}/01-{title}.md`, `/prompts/{topic}/02-{title}.md`, etc. + +**Required YAML frontmatter for each sub-prompt:** + +```yaml +--- +title: "Sub-Audit: {Title}" +filename: "/prompts/{topic}/01-{title}.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +prompt_type: "sub-prompt" +execution_order: 1 +parent_orchestrator: "/prompts/{topic}/00-ORCHESTRATOR.md" +related_report: "/reports/YYYY-MM-DD-{topic}/01-{title}.md" +--- +``` + +### Step 4B: Run Sub-Audits + +Execute each sub-prompt independently. Document findings in parallel. + +### Step 5B: Save Sub-Reports + +**File location:** `/reports/YYYY-MM-DD-{topic}/01-{title}.md`, etc. + +**Required YAML frontmatter:** + +```yaml +--- +title: "Report: {Sub-Audit Title}" +filename: "/reports/YYYY-MM-DD-{topic}/01-{title}.md" +created: "YYYY-MM-DD" +modified: "YYYY-MM-DD" +version: "1.0.0" +report_type: "audit" +related_prompt: "/prompts/{topic}/01-{title}.md" +parent_orchestrator_report: "/reports/YYYY-MM-DD-{topic}/00-CONSOLIDATED.md" +status: "complete" +--- +``` + +### Step 6B: Consolidate Findings + +**File location:** `/reports/YYYY-MM-DD-{topic}/00-CONSOLIDATED.md` + +**Consolidation structure:** +- Executive summary (findings across all sub-audits) +- Master findings register (merged from all sub-reports) +- Prioritized recommendations (high → low impact) +- Unified task list link + +### Step 7B: Extract Master Task List + +**File location:** `/tasks/{topic}-tasks.md` + +One task list per orchestrator. Tasks should be grouped by sub-audit or by priority. + +--- + +## Section 3: Archiving Completed Work + +**Use this when:** Task list is 100% complete, findings are implemented, work is done + +### Archive Checklist + +Before archiving, confirm: +- [ ] All tasks in task list are marked complete +- [ ] All findings have been addressed or explicitly deferred +- [ ] Report is finalized (no draft sections) +- [ ] No open questions or blockers + +### Archive Process + +**Step 1: Move report to archive** + +```bash +# Single-file report +mv /reports/{topic}.md /reports/archived/{topic}.md + +# Orchestrator report folder +mv /reports/YYYY-MM-DD-{topic}/ /reports/archived/YYYY-MM-DD-{topic}/ +``` + +**Step 2: Move task list to archive** + +```bash +# Task list +mv /tasks/{topic}-tasks.md /tasks/archived/{topic}-tasks.md +``` + +**Step 3: Update master task list** + +Edit `/tasks/master-task-list.md`: +- Move entry from "Active" section to "Completed (pending archive)" +- Add completion date + +**Step 4: Keep prompt for reference (optional)** + +Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. + +**Step 5: Clean up after 30 days** + +After task list is in "Completed" section for 30 days, permanently move to `/tasks/archived/`. + +--- + +## Critical Rules (Never Violate) + +### Rule 1: Never Delete `/tasks/task-list.md` + +``` +🚫 FORBIDDEN: +rm /tasks/task-list.md +git rm /tasks/task-list.md +``` + +This is the **master general-purpose task list**. It must always exist. + +**Why?** It's the catch-all for quick tasks that don't justify a dedicated orchestrator. Losing it breaks ongoing task tracking. + +**What to do instead:** +- Archive completed tasks within task-list.md (move to "Archived" section) +- Never delete the file itself +- Keep at least one active entry so the file is never empty + +### Rule 2: One Task List Per Orchestrator + +Each multi-step orchestrator prompt gets exactly one task list: +- `/tasks/{topic}-tasks.md` ← linked from prompt and report + +Don't create: +- ❌ `/tasks/{topic}-part-1.md` + `/tasks/{topic}-part-2.md` (split tasks) +- ❌ `/tasks/{topic}.md` + `/tasks/{topic}-followup.md` (orphaned followups) + +**Why?** Tracking is easier when all related tasks live in one file. + +### Rule 3: Frontmatter Is Always Required + +Every prompt, report, and task list starts with YAML frontmatter. No exceptions. + +**Required fields:** +- `title` — Human-readable title +- `filename` — Full path to this file +- `created` — ISO date (YYYY-MM-DD) +- `modified` — ISO date (YYYY-MM-DD) +- `version` — Semantic version (X.Y.Z) +- Context fields (prompt_type, report_type, related_prompt, etc.) + +Missing frontmatter means: +- ❌ Automation tools can't discover the file +- ❌ Versioning is broken +- ❌ Cross-references are unclear + +### Rule 4: Use Correct Folder Locations + +**No exceptions:** + +| Content | Location | Example | +|---------|----------|---------| +| Prompts | `/prompts/` | `/prompts/css-audit.md` | +| Reports | `/reports/` | `/reports/css-audit.md` or `/reports/2026-10-22-css-audit/` | +| Tasks | `/tasks/` | `/tasks/css-audit-tasks.md` | +| Archived | `/reports/archived/`, `/tasks/archived/` | `/reports/archived/2026-02-01-old-audit/` | + +**Never put:** +- ❌ Prompts in `/reports/` or `/docs/` +- ❌ Reports in `/prompts/` or root +- ❌ Tasks in `/reports/` or root + +--- + +## Templates + +### Template 1: Prompt Frontmatter (Single-File) + +**Location:** `templates/prompt-frontmatter-single.yml` + +Copy and customize: + +```yaml +--- +title: "Audit: {Your Title Here}" +filename: "/prompts/{topic}.md" +created: "2026-10-22" +modified: "2026-10-22" +version: "1.0.0" +prompt_type: "single-audit" +estimated_duration: "1 hour" +related_reports: "/reports/{topic}/" +related_tasks: "/tasks/{topic}-tasks.md" +--- +``` + +### Template 2: Report Frontmatter (Single-File) + +**Location:** `templates/report-frontmatter-single.yml` + +Copy and customize: + +```yaml +--- +title: "Report: {Your Title Here}" +filename: "/reports/{topic}.md" +created: "2026-10-22" +modified: "2026-10-22" +version: "1.0.0" +report_type: "audit" +related_prompt: "/prompts/{topic}.md" +related_tasks: "/tasks/{topic}-tasks.md" +status: "complete" +--- +``` + +### Template 3: Task List Frontmatter + +**Location:** `templates/task-frontmatter.yml` + +Copy and customize: + +```yaml +--- +title: "Task List: {Your Title Here}" +filename: "/tasks/{topic}-tasks.md" +created: "2026-10-22" +modified: "2026-10-22" +version: "1.0.0" +related_prompt: "/prompts/{topic}.md" +related_report: "/reports/{topic}.md" +status: "active" +--- +``` + +### Template 4: Orchestrator Frontmatter + +**Location:** `templates/orchestrator-frontmatter.yml` + +Copy and customize: + +```yaml +--- +title: "Orchestrator: {Your Title Here}" +filename: "/prompts/{topic}/00-ORCHESTRATOR.md" +created: "2026-10-22" +modified: "2026-10-22" +version: "1.0.0" +prompt_type: "orchestrator" +estimated_duration: "2 hours" +sub_prompts: ["01-first", "02-second", "03-third"] +related_reports: "/reports/2026-10-22-{topic}/" +related_tasks: "/tasks/{topic}-tasks.md" +--- +``` + +--- + +## References + +**Full documentation (for deep dives):** +- `guidelines/prompt-creation-guidelines.md` — Complete prompt spec +- `guidelines/report-creation-guidelines.md` — Complete report spec +- `guidelines/Guidelines.md` § "Default AI Workflow" — High-level workflow +- `guidelines/Guidelines.md` § "Mandatory Folder Conventions" — Folder rules +- `guidelines/Guidelines.md` § "Task list management conventions" — Archiving process + +**Related skills:** +- `/bem-css-compliance` — For CSS audits +- `/dark-mode-implementation` — For dark mode audits + +--- + +## Quick Start Checklist + +Running your first audit? + +- [ ] Decide: Single-file or orchestrator? +- [ ] Create `/prompts/{topic}.md` (or folder + 00-ORCHESTRATOR.md) +- [ ] Add required YAML frontmatter (copy from templates) +- [ ] Define scope, method, acceptance criteria +- [ ] Run audit; document findings +- [ ] Create `/reports/{topic}.md` with frontmatter +- [ ] Extract `/tasks/{topic}-tasks.md` +- [ ] Link all three files together (cross-reference in frontmatter) +- [ ] Begin implementing tasks +- [ ] Archive when 100% complete + +--- + +_Workflow orchestration skill for ThisOneTimeOnAcidCom audits and investigations._ diff --git a/guidelines/Guidelines.md b/guidelines/Guidelines.md index 6a70b9cc..4b28ba93 100644 --- a/guidelines/Guidelines.md +++ b/guidelines/Guidelines.md @@ -17,18 +17,14 @@ This document defines the core design, development, and technical guidelines for ### 🤖 Default AI Workflow (MUST FOLLOW) -**When asked to write a prompt, audit, or review, ALWAYS follow this sequence:** +**See the [Workflow Orchestration Skill](../../.claude/skills/workflow-orchestration/SKILL.md) for comprehensive guidance on:** +- Single-file audit workflows (4-step: prompt → audit → report → tasks) +- Multi-audit orchestrator workflows with parallel execution +- Folder structure and naming conventions +- YAML frontmatter templates for all content types +- Task list management and archiving procedures -1. **Create a prompt** in `/prompts/` — defines the audit scope, steps, and references to relevant guidelines. -2. **Run the audit** described in the prompt against the codebase and guidelines. -3. **Save findings** to a report file in `/reports/{topic}/` — only after the full audit is complete. -4. **Create a task list** in `/tasks/` — only once the report is finalized, extract actionable items into a checklist. - -**This is the assumed default.** You do not need to be told each step explicitly. When told to "write a prompt" or "audit X", execute the full 4-step workflow above. - -**Multi-audit orchestrators:** When an audit covers multiple areas, create a master/orchestrator prompt in `/prompts/{topic}/orchestrator.md` with individual sub-prompts. Each sub-audit gets its own report in `/reports/{topic}/`. All tasks are consolidated into one task list per orchestrator in `/tasks/`. - -**Reusability:** All prompts should be written as reusable templates that can be re-run for ongoing maintenance. +**Quick reference:** When told to "write a prompt" or "audit X", use the skill's decision tree to choose single-file or orchestrator workflow, then execute the full sequence (create prompt → run audit → save report → extract tasks). The skill provides reusable YAML templates and detailed step-by-step guidance. ### 🚫 Root Directory Restrictions (CRITICAL) @@ -53,25 +49,19 @@ This document defines the core design, development, and technical guidelines for ### 📁 Mandatory Folder Conventions -The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** Never place prompts, reports, or task lists anywhere else (e.g., never in root, never in `/guidelines/`). +The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** See the [Workflow Orchestration Skill](../../.claude/skills/workflow-orchestration/SKILL.md) for full folder structure rules and conventions. -| Folder | Purpose | Naming Convention | -|---|---|---| -| `/prompts/` | All prompt files for AI-assisted tasks | `{topic}.md` or subfolder `{topic}/` with `orchestrator.md` | -| `/reports/` | All audit findings, analysis results, reports | Subfolder per audit: `/reports/{audit-name}/` | -| `/tasks/` | All task lists and checklists | `task-list.md` is the master general-purpose task list | -| `/docs/` | General project documentation, quick references, attributions | Descriptive filenames (e.g., `Attributions.md`, `quick-reference.md`) | -| `/scripts/` | All build, utility, and automation scripts (`.ts`, `.sh`, `.js`) | Descriptive filenames (e.g., `verify-build.ts`, `deploy.sh`) | +**Quick Reference:** -**Rules:** +| Folder | Purpose | +|---|---| +| `/prompts/` | All prompt files for AI-assisted tasks | +| `/reports/` | All audit findings, analysis results, reports | +| `/tasks/` | All task lists and checklists; `/tasks/task-list.md` is the persistent master | +| `/docs/` | General project documentation, quick references, attributions | +| `/scripts/` | All build, utility, and automation scripts | -1. **Prompts:** Always create new prompt files in `/prompts/`. For multi-step workflows, create a subfolder with a master `orchestrator.md` and child prompt files. -2. **Reports:** Always write reports to `/reports/`, inside a suitable subfolder (e.g., `/reports/root-cleanup/`, `/reports/css-audit/`). One subfolder per audit or topic. -3. **Tasks:** Always create task lists in `/tasks/`. The file `/tasks/task-list.md` is the **all-purpose general task list** — it must never be deleted. One task list per orchestrator prompt, stored in the root of `/tasks/`. -4. **Lifecycle:** Archive completed tasks for later reference. Delete any report older than a few days. Regularly review all folders for unused and orphaned files. -5. **Cross-referencing:** When referencing guidelines from prompts/reports/tasks, always link to the specific guideline file (e.g., `[BEM Architecture](../guidelines/css-architecture.md)`). -6. **Never delete** `/tasks/task-list.md` — it is the persistent master checklist. -7. **Docs:** The `/docs/` folder is the designated home for all general-purpose project documentation, quick references, guides, and relocated documentation files (e.g., CMS field mappings, architecture overviews). Any `.md` file that does not belong in `/guidelines/`, `/prompts/`, `/reports/`, or `/tasks/` should go in `/docs/`. +**Critical rule:** Never delete `/tasks/task-list.md` — it is the persistent master checklist. ### 🛡️ Bundler Compatibility Rules (Figma Make) diff --git a/guidelines/README.md b/guidelines/README.md index f65c79f8..0f186ad9 100644 --- a/guidelines/README.md +++ b/guidelines/README.md @@ -36,7 +36,7 @@ Follow this **exact reading order** to understand the design system: 14. **[design-tokens/spacing.md](./design-tokens/spacing.md)** - Spacing system #### Step 4: Understand Data System (REQUIRED) -15. **[Data System Documentation](../data/README.md)** - Mock data system and centralized content management +15. **[Data System Documentation](./data-models.md)** - Data model definitions and centralized content management #### Step 5: Read Theme Documentation (REQUIRED) 16. **[dark-mode-implementation.md](./dark-mode-implementation.md)** - Complete dark mode implementation @@ -174,7 +174,7 @@ guidelines/ **Building a Page Component?** - Start with [overview-components.md](./overview-components.md) -- Check [Data System Documentation](../data/README.md) for content +- Check [data-models.md](./data-models.md) for content structure - Review [Guidelines.md](./Guidelines.md) Section 1 for architecture **Using a Specific Component?** diff --git a/guidelines/events-system.md b/guidelines/events-system.md index 60795b5d..c4aa1130 100644 --- a/guidelines/events-system.md +++ b/guidelines/events-system.md @@ -1,3 +1,12 @@ +--- +title: "Events System — Data Model & Architecture Guidelines" +filename: "/guidelines/events-system.md" +created: "2026-02-01" +modified: "2026-10-22" +version: "1.0.0" +status: "complete" +--- + # Events System — Data Model & Architecture Guidelines **Version:** 1.0.0 diff --git a/guidelines/wordpress-block-patterns.md b/guidelines/wordpress-block-patterns.md index faed21ee..cf116eaf 100644 --- a/guidelines/wordpress-block-patterns.md +++ b/guidelines/wordpress-block-patterns.md @@ -1,3 +1,12 @@ +--- +title: "WordPress Block Pattern Mapping" +filename: "/guidelines/wordpress-block-patterns.md" +created: "2026-02-01" +modified: "2026-10-22" +version: "1.0.0" +status: "complete" +--- + # WordPress Block Pattern Mapping **Version:** 1.0.0 From 7a3bd9bcb62eb519efec6eacc63b23bfa25f3f64 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 02:30:15 +0000 Subject: [PATCH 2/7] Fix CodeRabbit review findings on Workflow Orchestration Skill MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Use repository-relative paths (./reports/..., ./tasks/...) instead of filesystem-root paths - Align report path convention: /reports/{topic}/report.md (file in folder) consistently - Remove premature task-list move from Step 2; keep 30-day retention in Step 4 - Require prompts to MUST link specific guideline files in Related Guidelines section - Fix broken relative paths in Guidelines.md: ../../.claude/ → ../.claude/ All changes maintain consistency with repository folder conventions and improve maintainability. Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .../skills/workflow-orchestration/SKILL.md | 24 +++++++------------ guidelines/Guidelines.md | 4 ++-- 2 files changed, 11 insertions(+), 17 deletions(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index d9886148..e33b152b 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -130,14 +130,14 @@ Execute the audit prompt against the codebase. The AI will follow your methodolo ### Step 3A: Save the Report -**File location:** `/reports/{topic}.md` (single file, root of /reports/) +**File location:** `/reports/{topic}/report.md` (single file inside topic folder) **Required YAML frontmatter:** ```yaml --- title: "Audit Title Report" -filename: "/reports/{topic}.md" +filename: "/reports/{topic}/report.md" created: "YYYY-MM-DD" modified: "YYYY-MM-DD" version: "1.0.0" @@ -394,32 +394,25 @@ Before archiving, confirm: ```bash # Single-file report -mv /reports/{topic}.md /reports/archived/{topic}.md +mv ./reports/{topic}.md ./reports/archived/{topic}.md # Orchestrator report folder -mv /reports/YYYY-MM-DD-{topic}/ /reports/archived/YYYY-MM-DD-{topic}/ -``` - -**Step 2: Move task list to archive** - -```bash -# Task list -mv /tasks/{topic}-tasks.md /tasks/archived/{topic}-tasks.md +mv ./reports/YYYY-MM-DD-{topic}/ ./reports/archived/YYYY-MM-DD-{topic}/ ``` -**Step 3: Update master task list** +**Step 2: Update master task list** Edit `/tasks/master-task-list.md`: - Move entry from "Active" section to "Completed (pending archive)" - Add completion date -**Step 4: Keep prompt for reference (optional)** +**Step 3: Keep prompt for reference (optional)** Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. -**Step 5: Clean up after 30 days** +**Step 4: Clean up after 30 days** -After task list is in "Completed" section for 30 days, permanently move to `/tasks/archived/`. +After task list is in "Completed" section for 30 days, permanently move to `./tasks/archived/`. --- @@ -464,6 +457,7 @@ Every prompt, report, and task list starts with YAML frontmatter. No exceptions. - `modified` — ISO date (YYYY-MM-DD) - `version` — Semantic version (X.Y.Z) - Context fields (prompt_type, report_type, related_prompt, etc.) +- If a prompt relies on project guidance, it MUST link each specific guideline file that it uses in a `Related Guidelines` section Missing frontmatter means: - ❌ Automation tools can't discover the file diff --git a/guidelines/Guidelines.md b/guidelines/Guidelines.md index 4b28ba93..d89fd374 100644 --- a/guidelines/Guidelines.md +++ b/guidelines/Guidelines.md @@ -17,7 +17,7 @@ This document defines the core design, development, and technical guidelines for ### 🤖 Default AI Workflow (MUST FOLLOW) -**See the [Workflow Orchestration Skill](../../.claude/skills/workflow-orchestration/SKILL.md) for comprehensive guidance on:** +**See the [Workflow Orchestration Skill](../.claude/skills/workflow-orchestration/SKILL.md) for comprehensive guidance on:** - Single-file audit workflows (4-step: prompt → audit → report → tasks) - Multi-audit orchestrator workflows with parallel execution - Folder structure and naming conventions @@ -49,7 +49,7 @@ This document defines the core design, development, and technical guidelines for ### 📁 Mandatory Folder Conventions -The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** See the [Workflow Orchestration Skill](../../.claude/skills/workflow-orchestration/SKILL.md) for full folder structure rules and conventions. +The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** See the [Workflow Orchestration Skill](../.claude/skills/workflow-orchestration/SKILL.md) for full folder structure rules and conventions. **Quick Reference:** From 06d6f266ebc36fc16fc105f9ba52cfc2cee2d7f7 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 03:22:36 +0000 Subject: [PATCH 3/7] fix: correct task-list path reference in workflow-orchestration skill Line 405 now correctly references /tasks/task-list.md (the persistent master list) instead of /tasks/master-task-list.md, ensuring users update the authoritative task list. Addresses CodeRabbit finding: TM1-405 Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .claude/skills/workflow-orchestration/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index e33b152b..f6978431 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -402,7 +402,7 @@ mv ./reports/YYYY-MM-DD-{topic}/ ./reports/archived/YYYY-MM-DD-{topic}/ **Step 2: Update master task list** -Edit `/tasks/master-task-list.md`: +Edit `/tasks/task-list.md`: - Move entry from "Active" section to "Completed (pending archive)" - Add completion date From dfb69b47a8ca3a267fde04323ee645069edb9866 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 03:36:27 +0000 Subject: [PATCH 4/7] fix: add 30-day report retention and master task list tracking to archiving steps - Step 1: Clarify that reports must wait 30 days after completion before archiving - Step 2: Add instructions to update /tasks/master-task-list.md for dedicated orchestrator task lists - Step 4: Include master-task-list.md update for final archived locations - Step 7B: Add registration requirement for new dedicated task lists in master list Addresses CodeRabbit findings: report retention window and dedicated task tracking. Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .../skills/workflow-orchestration/SKILL.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index f6978431..f97e4ee2 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -374,6 +374,14 @@ status: "complete" One task list per orchestrator. Tasks should be grouped by sub-audit or by priority. +**Register in master task list:** + +When the dedicated task list is created, add its entry to `/tasks/master-task-list.md` under "Active": +- Link: `/tasks/{topic}-tasks.md` +- Related report: `/reports/YYYY-MM-DD-{topic}/` (orchestrator report folder) +- Status: Active +- Created date: YYYY-MM-DD + --- ## Section 3: Archiving Completed Work @@ -390,7 +398,9 @@ Before archiving, confirm: ### Archive Process -**Step 1: Move report to archive** +**Step 1: After 30 days have passed since completion, move the report to archive** + +Do not move the report before the 30-day post-completion retention period ends. ```bash # Single-file report @@ -406,6 +416,11 @@ Edit `/tasks/task-list.md`: - Move entry from "Active" section to "Completed (pending archive)" - Add completion date +If this is an orchestrator audit with dedicated task lists: +- Also update `/tasks/master-task-list.md` +- Move the dedicated task-list entry from "Active" to "Completed (pending archive)" +- Add completion date and location of the dedicated task list (e.g., `/tasks/{topic}-tasks.md`) + **Step 3: Keep prompt for reference (optional)** Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. @@ -414,6 +429,8 @@ Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. After task list is in "Completed" section for 30 days, permanently move to `./tasks/archived/`. +Also update `/tasks/master-task-list.md` with final archived location of any dedicated orchestrator task lists. + --- ## Critical Rules (Never Violate) From a424b5c855877fb75a41add470945b523afe1175 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 03:48:19 +0000 Subject: [PATCH 5/7] fix: Move task-list status update to completion step, before 30-day retention MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix CodeRabbit Finding A: Move task-list status update from Archive Step 2 to new Step 8 * Status 'Active' → 'Completed (pending archive)' now happens at task completion * This occurs BEFORE the 30-day retention period begins (per repository convention) * Archive Process Step 2 now only handles final archive location tracking * This fixes the workflow step ordering violation - Fix CodeRabbit Finding B: Update Guidelines.md report archive guidance * Added '30-day wait' requirement to report archiving process * Aligns operative guidance with 30-day post-completion retention requirement * Ensures Guidelines.md and SKILL.md are consistent SKILL.md changes: - Added Step 8: 'Mark Task List as Complete' (new section after Step 7B) - Clarified that status updates happen immediately upon completion - Defines what to update in both task-list.md and master-task-list.md - Modified Archive Process Step 2 to track final archive locations only - Updated Archive Process Step 4 with permanent deletion guidance Guidelines.md changes: - Updated report archiving instruction to include 30-day wait requirement - Changed from 'When complete, move...' to 'Wait 30 days from completion, then move...' Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .../skills/workflow-orchestration/SKILL.md | 38 +++++++++++++++---- guidelines/Guidelines.md | 2 +- 2 files changed, 31 insertions(+), 9 deletions(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index f97e4ee2..34112246 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -382,6 +382,23 @@ When the dedicated task list is created, add its entry to `/tasks/master-task-li - Status: Active - Created date: YYYY-MM-DD +### Step 8: Mark Task List as Complete + +**When:** All tasks in the task list are marked complete (100% done) + +**Do this immediately upon completion, BEFORE the 30-day retention period begins:** + +**Update `/tasks/task-list.md`:** +- Move entry from "Active" section to "Completed (pending archive)" +- Add completion date: YYYY-MM-DD + +**If this is an orchestrator audit with dedicated task lists:** +- Also update `/tasks/master-task-list.md` +- Move the dedicated task-list entry from "Active" to "Completed (pending archive)" +- Add completion date and location of the dedicated task list (e.g., `/tasks/{topic}-tasks.md`) + +**Important:** Status changes to "Completed (pending archive)" happen at task completion, not during archiving. This marks the start of the mandatory 30-day retention period before files can be moved to the archive folder. + --- ## Section 3: Archiving Completed Work @@ -410,26 +427,31 @@ mv ./reports/{topic}.md ./reports/archived/{topic}.md mv ./reports/YYYY-MM-DD-{topic}/ ./reports/archived/YYYY-MM-DD-{topic}/ ``` -**Step 2: Update master task list** +**Step 2: Update archive location tracking** + +Both `/tasks/task-list.md` and `/tasks/master-task-list.md` should already have status "Completed (pending archive)" from Step 8 (marked at task completion). Now that files are being permanently archived, update the final archive locations: Edit `/tasks/task-list.md`: -- Move entry from "Active" section to "Completed (pending archive)" -- Add completion date +- Move entry from "Completed (pending archive)" section to "Archived" +- Add archive date: YYYY-MM-DD If this is an orchestrator audit with dedicated task lists: - Also update `/tasks/master-task-list.md` -- Move the dedicated task-list entry from "Active" to "Completed (pending archive)" -- Add completion date and location of the dedicated task list (e.g., `/tasks/{topic}-tasks.md`) +- Move the dedicated task-list entry from "Completed (pending archive)" to "Archived" +- Update path from `/tasks/{topic}-tasks.md` to `/tasks/archived/{topic}-tasks.md` +- Add archive date **Step 3: Keep prompt for reference (optional)** Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. -**Step 4: Clean up after 30 days** +**Step 4: Permanent deletion (optional, 30+ days after archiving)** -After task list is in "Completed" section for 30 days, permanently move to `./tasks/archived/`. +After task list entries have been in "Archived" section for 30 additional days (60 days total from original completion), you may permanently delete: +- The archived task list file (e.g., `/tasks/archived/{topic}-tasks.md`) +- References in `/tasks/master-task-list.md` may also be removed -Also update `/tasks/master-task-list.md` with final archived location of any dedicated orchestrator task lists. +**Best practice:** Keep archived task lists and references for 60+ days total to preserve audit trail, then clean up as needed. --- diff --git a/guidelines/Guidelines.md b/guidelines/Guidelines.md index d89fd374..577dc071 100644 --- a/guidelines/Guidelines.md +++ b/guidelines/Guidelines.md @@ -119,7 +119,7 @@ The Figma Make bundler has known syntax incompatibilities. **All code MUST follo 3. Only delete from `/tasks/archived/` — never delete active or recently completed task lists **Report archiving process:** -1. When a report's associated task list is 100% complete, move the report folder from `/reports/{topic}/` to `/reports/archived/{topic}/` +1. When a report's associated task list is 100% complete, wait 30 days from completion, then move the report folder from `/reports/{topic}/` to `/reports/archived/{topic}/` 2. Reports in `/reports/archived/` can be deleted after 7 days 3. Only delete from `/reports/archived/` — never delete active reports From 37ee16487d8b97310ece29df29cb1974d6df4428 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 22 Oct 2026 03:59:57 +0000 Subject: [PATCH 6/7] fix: Add single-file task list registration, task-file archiving, and tombstone retention MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix Finding 1 (Line 441-442): Archive Process Step 2 now moves the task-list file * Add instruction to move /tasks/{topic}-tasks.md to /tasks/archived/{topic}-tasks.md * Move file BEFORE updating tracker paths (data integrity) * Ensures tracker path correctly points to moved file location - Fix Finding 2 (Line 432): Single-file audits now register in master tracker * Add Step 4B: Register single-file task lists in /tasks/master-task-list.md * Single-file lists now follow same lifecycle as orchestrator lists * Ensures consistent completion → retention → archive workflow - Fix Finding 3 (Line 452): Retain tombstone entries for deletion history * Changed Step 4 permanent deletion guidance * No longer removes references from master-task-list.md * Replaces with tombstone entry showing deleted status + date * Preserves audit trail of all task lists and their lifecycle These changes ensure: - ✅ Task files physically moved before tracker paths updated - ✅ All task list types tracked consistently - ✅ Complete audit history maintained via tombstones Co-Authored-By: Claude Haiku 4.5 Claude-Session: https://claude.ai/code/session_01RargWXCrM2LpVtBTXiZcVa --- .../skills/workflow-orchestration/SKILL.md | 47 +++++++++++++++++-- 1 file changed, 42 insertions(+), 5 deletions(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index 34112246..3da4b030 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -216,6 +216,20 @@ Refactor Tailwind utilities to BEM classes across `/styles/blocks/`. 10 tasks, ~ 2026-11-01 (4 hours, 2 developers) ``` +### Step 4B: Register Single-File Task List + +**When:** Immediately after creating `/tasks/{topic}-tasks.md` + +Single-file audits must also register their task lists in the master tracker for lifecycle management: + +**Update `/tasks/master-task-list.md` under "Active":** +- Link: `/tasks/{topic}-tasks.md` +- Related report: `/reports/{topic}/report.md` (single-file report) +- Status: Active +- Created date: YYYY-MM-DD + +**Why:** Both single-file and orchestrator task lists follow the same completion → retention → archive → tombstone lifecycle. The master tracker must cover all dedicated task lists so completion status updates and archiving can proceed consistently. + --- ## Section 2: Orchestrator Workflow @@ -427,9 +441,21 @@ mv ./reports/{topic}.md ./reports/archived/{topic}.md mv ./reports/YYYY-MM-DD-{topic}/ ./reports/archived/YYYY-MM-DD-{topic}/ ``` -**Step 2: Update archive location tracking** +**Step 2: Move task-list file to archive, then update tracker** + +Both `/tasks/task-list.md` and `/tasks/master-task-list.md` should already have status "Completed (pending archive)" from Step 8 (marked at task completion). Now that files are being permanently archived: -Both `/tasks/task-list.md` and `/tasks/master-task-list.md` should already have status "Completed (pending archive)" from Step 8 (marked at task completion). Now that files are being permanently archived, update the final archive locations: +**First, move the completed task-list file:** + +```bash +# Single-file audit (if a dedicated list was created) +mv ./tasks/{topic}-tasks.md ./tasks/archived/{topic}-tasks.md + +# Orchestrator audit (if dedicated orchestrator list exists) +mv ./tasks/{topic}-tasks.md ./tasks/archived/{topic}-tasks.md +``` + +**Then, update archive location tracking in the master tracker:** Edit `/tasks/task-list.md`: - Move entry from "Completed (pending archive)" section to "Archived" @@ -438,7 +464,7 @@ Edit `/tasks/task-list.md`: If this is an orchestrator audit with dedicated task lists: - Also update `/tasks/master-task-list.md` - Move the dedicated task-list entry from "Completed (pending archive)" to "Archived" -- Update path from `/tasks/{topic}-tasks.md` to `/tasks/archived/{topic}-tasks.md` +- Update path from `/tasks/{topic}-tasks.md` to `/tasks/archived/{topic}-tasks.md` (reflecting the moved file) - Add archive date **Step 3: Keep prompt for reference (optional)** @@ -449,9 +475,20 @@ Prompts can stay in `/prompts/` for re-running. Leave as-is unless superseded. After task list entries have been in "Archived" section for 30 additional days (60 days total from original completion), you may permanently delete: - The archived task list file (e.g., `/tasks/archived/{topic}-tasks.md`) -- References in `/tasks/master-task-list.md` may also be removed -**Best practice:** Keep archived task lists and references for 60+ days total to preserve audit trail, then clean up as needed. +**For `/tasks/master-task-list.md`:** Do NOT remove references. Instead, retain a **tombstone entry** that records: +- Original link: `/tasks/{topic}-tasks.md` +- Archived location (if moved): `/tasks/archived/{topic}-tasks.md` +- Status: **Deleted** +- Deletion date: YYYY-MM-DD +- Reason: (e.g., "Archived after 60-day retention period") + +**Example tombstone entry:** +``` +| `/tasks/css-audit-tasks.md` | `/tasks/archived/css-audit-tasks.md` | **Deleted** | 2026-12-21 | Archived after 60-day retention | +``` + +**Why:** Preserving deletion history in the master tracker maintains an audit trail of all task lists, their lifecycle, and when they were removed from active use. --- From cec43058b050ea343c6771431b219897fa2f192a Mon Sep 17 00:00:00 2001 From: "coderabbitai[bot]" <136622811+coderabbitai[bot]@users.noreply.github.com> Date: Thu, 22 Oct 2026 04:24:06 +0000 Subject: [PATCH 7/7] fix: Keep the persistent task checklist active and archive only dedicated task lists --- .../skills/workflow-orchestration/SKILL.md | 20 ++++++------------- 1 file changed, 6 insertions(+), 14 deletions(-) diff --git a/.claude/skills/workflow-orchestration/SKILL.md b/.claude/skills/workflow-orchestration/SKILL.md index 3da4b030..fef9de26 100644 --- a/.claude/skills/workflow-orchestration/SKILL.md +++ b/.claude/skills/workflow-orchestration/SKILL.md @@ -402,16 +402,13 @@ When the dedicated task list is created, add its entry to `/tasks/master-task-li **Do this immediately upon completion, BEFORE the 30-day retention period begins:** -**Update `/tasks/task-list.md`:** -- Move entry from "Active" section to "Completed (pending archive)" -- Add completion date: YYYY-MM-DD - -**If this is an orchestrator audit with dedicated task lists:** -- Also update `/tasks/master-task-list.md` +**For a dedicated task list (single-file or orchestrator audit), update `/tasks/master-task-list.md`:** - Move the dedicated task-list entry from "Active" to "Completed (pending archive)" - Add completion date and location of the dedicated task list (e.g., `/tasks/{topic}-tasks.md`) -**Important:** Status changes to "Completed (pending archive)" happen at task completion, not during archiving. This marks the start of the mandatory 30-day retention period before files can be moved to the archive folder. +**For tasks in `/tasks/task-list.md`:** Mark the relevant checkboxes complete and record their completion date. Keep this persistent checklist and its tracker entry active (ongoing general-purpose); do not apply "Completed (pending archive)" to either. + +**Important:** The dedicated audit entry changes to "Completed (pending archive)" at task completion, not during archiving. Its completion date marks the start of the mandatory 30-day retention period before the dedicated task list and associated reports can be moved to the archive folder. --- @@ -443,7 +440,7 @@ mv ./reports/YYYY-MM-DD-{topic}/ ./reports/archived/YYYY-MM-DD-{topic}/ **Step 2: Move task-list file to archive, then update tracker** -Both `/tasks/task-list.md` and `/tasks/master-task-list.md` should already have status "Completed (pending archive)" from Step 8 (marked at task completion). Now that files are being permanently archived: +For a dedicated task list, its audit entry in `/tasks/master-task-list.md` should already be in "Completed (pending archive)" from Step 8 (marked at task completion). Only dedicated task-list files are moved below. Keep `/tasks/task-list.md` in place and its tracker entry active (ongoing general-purpose). **First, move the completed task-list file:** @@ -457,12 +454,7 @@ mv ./tasks/{topic}-tasks.md ./tasks/archived/{topic}-tasks.md **Then, update archive location tracking in the master tracker:** -Edit `/tasks/task-list.md`: -- Move entry from "Completed (pending archive)" section to "Archived" -- Add archive date: YYYY-MM-DD - -If this is an orchestrator audit with dedicated task lists: -- Also update `/tasks/master-task-list.md` +For a dedicated task list (single-file or orchestrator audit), edit `/tasks/master-task-list.md`: - Move the dedicated task-list entry from "Completed (pending archive)" to "Archived" - Update path from `/tasks/{topic}-tasks.md` to `/tasks/archived/{topic}-tasks.md` (reflecting the moved file) - Add archive date