Revert "templates live docs"

This reverts commit cb3f73f.

Author: thompson0012

templates/base/docs/live/progress.md

@@ -4,34 +4,41 @@ Read after `docs/live/current-focus.md` to recover the latest state, continuity,
 
 ## Current State
 
-Summarize the current state of the work in 1-2 sentences.
+The template skill surface now has a complete top-level discoverability pass: `using-agent-practices` and its category map cover every live top-level skill, including standalone specialist leaves that were previously omitted. No package moves or new router families were needed, so the default next move still returns to Task 35 unless a concrete routing regression appears.
 
 ## Latest Completed Work
 
-- completed item
+- completed a full scan of `templates/base/.agents/skills/` and found six live top-level skills missing from the canonical top-level router surface: `create-skill`, `create-router-skill`, `cx-ticket-triage`, `data-exploration`, `visualization`, and `media`
+- updated `templates/base/.agents/skills/using-agent-practices/{SKILL.md,references/category-map.md,evals/*}` so those skills are first-class direct routes with explicit boundary language against nearby skills
+- updated `templates/base/docs/reference/{codemap.md,memory.md}` to preserve the top-level discoverability rule and the category-map role
+- reviewed reference writeback: no `templates/base/docs/reference/{architecture.md,lessons.md}` update was needed because the change tightened top-level discoverability rules without moving package boundaries or adding a new failure-pattern worth preserving
 
 ## In Progress
 
-- none
+None.
 
 ## Blockers
 
-- none
+None.
 
 ## Next Recommended Action
 
-- Next step:
+- Next step: Resume Task 35: refine the capability-based methodology overlays in the finance, research, and webapp docs. Treat the top-level skill audit as landed unless a concrete discoverability regression appears.
 
 ## Touched Files
 
-- `path/to/file`
+- `templates/base/.agents/skills/using-agent-practices/`
+- `templates/base/docs/reference/{codemap.md,memory.md}`
+- `templates/base/docs/live/progress.md`
 
 ## Verification Status
 
-- Check:
-- Result:
+- Check: `python3 templates/base/.agents/skills/create-skill/scripts/validate.py --strict templates/base/.agents/skills/using-agent-practices`
+- Result: passed
+- Check: targeted Python assertions for top-level skill coverage, router outputs, category-map inventory completeness, and eval IDs
+- Result: passed
 
 ## Hand-off Note
 
-- Resume from:
-- Watch for:
+- Resume from: `templates/base/.agents/skills/using-agent-practices/` if any top-level routing ambiguity resurfaces; otherwise return to Task 35 work.
+- Watch for: future standalone skills added under `templates/base/.agents/skills/` without matching updates to `using-agent-practices/SKILL.md`, `references/category-map.md`, and trigger/task eval coverage.

templates/base/docs/reference/architecture.md

@@ -45,9 +45,5 @@ Read when system shape, boundaries, or invariants matter. Keep this focused on s
 - Key dependency: an independent evaluator or explicit acceptance pass writing the record as it verifies.
 
 - Component: `.agents/skills/software-delivery/`
-- Responsibility: routes non-trivial software work between feature discovery, multi-phase control, harness control, plan reviews, and independent frontend evaluation.
+- Responsibility: routes non-trivial software work between feature discovery, harness control, plan reviews, and independent frontend evaluation.
 - Key dependency: the request being classified by the dominant delivery need rather than by convenience.
-
-- Component: `.agents/skills/software-delivery/multi-phase-control/`
-- Responsibility: preserves roadmap intent across phases with explicit phase gates, drift tracking, compaction checkpoints, and live-doc persistence.
-- Key dependency: the control model and baton ownership rules staying aligned with `harness-design` and `context-compaction`.

templates/base/docs/reference/codemap.md

@@ -16,10 +16,6 @@ Read when you need to find where to work. Prefer only high-value paths.
 - Purpose: router family for feature discovery, harness control, plan reviews, and independent frontend evaluation.
 - Update when: a software-delivery leaf is added, removed, renamed, or materially repurposed.
 
-- Path: `templates/base/.agents/skills/software-delivery/multi-phase-control/`
-- Purpose: leaf skill for phase-gated persistence, drift tracking, and cross-session roadmap continuity.
-- Update when: the multi-phase workflow, templates, or router bindings change.
-
 - Path: `templates/base/.agents/skills/using-reasoning/`
 - Purpose: router family for analytical requests across state calibration, problem framing, strategic foresight, hidden-rule reality checks, structured advisory, and multi-lens analysis.
 - Update when: a reasoning leaf is added, removed, renamed, or materially repurposed.
@@ -41,7 +37,7 @@ Read when you need to find where to work. Prefer only high-value paths.
 
 - Entrypoint: `templates/base/.agents/skills/software-delivery/SKILL.md`
 - Consumer: agents choosing the right software-delivery lane
-- Notes: routes to `feature-discovery`, `multi-phase-control`, `harness-design`, `plan-product-review`, `plan-engineering-review`, `plan-design-review`, or `frontend-evaluator`.
+- Notes: routes to `feature-discovery`, `harness-design`, `plan-product-review`, `plan-engineering-review`, `plan-design-review`, or `frontend-evaluator`.
 
 - Entrypoint: `templates/base/.agents/skills/using-reasoning/SKILL.md`
 - Consumer: agents choosing the right reasoning lane for analytical, strategic, or diagnostic requests

templates/base/docs/reference/lessons.md

@@ -17,7 +17,3 @@ Read after mistakes, rework, or surprises. Capture only reusable lessons.
 - Fix:
 - When to apply:
 - Evidence:
-
-- Fix: write router and skill edits under `templates/base/`, not the user-home copy, and remove any accidental repo-root `.agents/` duplicate before verifying.
-- When to apply: whenever scaffolding or copying skill packages in this repository.
-- Evidence: this task initially wrote to the wrong location and left a duplicate tree until the repo-root copy was deleted.

templates/base/docs/reference/memory.md

@@ -12,7 +12,3 @@ Read for durable truths worth preserving across sessions. Do not store transient
 - Decision: `using-agent-practices` is the canonical top-level discoverability router for the template skill suite, and its `references/category-map.md` inventory must stay in sync with every live top-level skill under `templates/base/.agents/skills/`.
 - Preserve because: missing standalone leaves in the top-level router create silent discovery holes even when the skills themselves are valid and present on disk.
 - Revisit only if: the template adopts a different top-level discovery mechanism or moves standalone specialist skills behind a new explicit family router.
-
-- Decision: `software-delivery/multi-phase-control` is the canonical leaf for phase-gated roadmap persistence and drift prevention, and `software-delivery` routes to it before `harness-design` when preserving original intent across phases is the primary need.
-- Preserve because: multi-phase work fails when original intent lives only in chat context instead of an explicit persistence workflow.
-- Revisit only if: phase preservation becomes part of another router or a new control model replaces the current multi-phase workflow.