refactor(skills): use .agents/ instead of .agent/ for phased execution

Standardize on the .agents/ directory across all phased-execution
skills (phase state, reports, sessions, validate.sh, PLAN.md, and
per-story/feature/workflow trees). Legacy dot-less agent/ fallbacks
in migration scripts are untouched.

new-project/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: new-project
-description: Initialises a new Python project and its high-rigor, phased-execution roadmap for a chosen project type. Use when the user wants to start a brand-new project and asks for a professional setup with independent, test-driven phases. Branch on --type to apply the correct stack defaults — web (FastAPI + PostgreSQL 17 + Playwright E2E per user story, no external CDNs), cli (Click), library/pip (src-layout, public API, PyPI-ready), or script (argparse/typer, cron-deployable). This skill scaffolds the environment AND writes the .agent/phases roadmap; the phase-authoring skill adds phases later and the phased-execution skill runs them.
+description: Initialises a new Python project and its high-rigor, phased-execution roadmap for a chosen project type. Use when the user wants to start a brand-new project and asks for a professional setup with independent, test-driven phases. Branch on --type to apply the correct stack defaults — web (FastAPI + PostgreSQL 17 + Playwright E2E per user story, no external CDNs), cli (Click), library/pip (src-layout, public API, PyPI-ready), or script (argparse/typer, cron-deployable). This skill scaffolds the environment AND writes the .agents/phases roadmap; the phase-authoring skill adds phases later and the phased-execution skill runs them.
 ---
 
 # New Project
@@ -28,9 +28,9 @@ Determine `--type` from the chat context (or ask once if genuinely absent):
 
 ## Phase state in files
 
-- `.agent/PLAN.md` — master design; **LOCKED DECISIONS** are binding.
-- `.agent/phases/todo/NN_name/` — pending phase: `00_phase.md` + `NN_task.md` files.
-- `.agent/phases/complete/` — finished phases (mirrors `todo/`, read-only history).
+- `.agents/PLAN.md` — master design; **LOCKED DECISIONS** are binding.
+- `.agents/phases/todo/NN_name/` — pending phase: `00_phase.md` + `NN_task.md` files.
+- `.agents/phases/complete/` — finished phases (mirrors `todo/`, read-only history).
 - `AGENTS.md` — project operating rules derived from this skill's mandates.
 
 ## Protocol — New Project
@@ -60,7 +60,7 @@ applying **only your branch's** stack section.
 
 #### Common (all types)
 - `uv` project: `pyproject.toml`, `src/<name>/` package layout, `[project.scripts]` entry point where a CLI/library applies.
-- `.gitignore` that **includes `.agent/phase-sessions/` and `.agent/pipeline.log`** — but never `.agent/` itself (the phase roadmap is tracked and committed).
+- `.gitignore` that **includes `.agents/phase-sessions/` and `.agents/pipeline.log`** — but never `.agents/` itself (the phase roadmap is tracked and committed).
 - Multi-stage `Containerfile` (assumes `podman`/`docker`).
 - `README.md` with `uv` + configuration instructions.
 - **Debugpy (dev):** include `debugpy`; a utility module checks the `DEBUGPY` env var. Default (`DEBUGPY=0`/unset) → **not** imported, minimal overhead. `DEBUGPY=1` → import and listen (e.g. port 5678) without blocking.
@@ -117,17 +117,17 @@ anchors are the only technologies phases may use. Cover:
 
 Create with file tools:
 
-- **`.agent/PLAN.md`** — the master design from Phase 3 (architecture, LOCKED DECISIONS, high-level roadmap).
-- **`AGENTS.md`** — initialized with: read `.agent/PLAN.md` first; follow the phased protocol in `.agent/phases/`; never modify `PLAN.md` or anything in `.agent/phases/complete/`; ask before editing `todo/`; adhere to the LOCKED DECISIONS.
-- **`.agent/phases/todo/`** — sequential phase directories (`01_…/`, `02_…/`, …), each with a `00_phase.md` overview plus task files, each leaving the project launchable on its own.
-- **`.agent/phases/complete/`** — create, leave empty.
+- **`.agents/PLAN.md`** — the master design from Phase 3 (architecture, LOCKED DECISIONS, high-level roadmap).
+- **`AGENTS.md`** — initialized with: read `.agents/PLAN.md` first; follow the phased protocol in `.agents/phases/`; never modify `PLAN.md` or anything in `.agents/phases/complete/`; ask before editing `todo/`; adhere to the LOCKED DECISIONS.
+- **`.agents/phases/todo/`** — sequential phase directories (`01_…/`, `02_…/`, …), each with a `00_phase.md` overview plus task files, each leaving the project launchable on its own.
+- **`.agents/phases/complete/`** — create, leave empty.
 
-Do **not** create `.agent/validate.sh` — the `phased-execution` skill installs it
+Do **not** create `.agents/validate.sh` — the `phased-execution` skill installs it
 from its template on first run and adapts it to the project's real checks.
 
 - **Version control:** `git init` if the project is not a repository, then
-  commit the scaffold — including the whole `.agent/` tree (tracked, never
-  git-ignored; only `.agent/phase-sessions/` and `.agent/pipeline.log` are
+  commit the scaffold — including the whole `.agents/` tree (tracked, never
+  git-ignored; only `.agents/phase-sessions/` and `.agents/pipeline.log` are
   ignored) — with a Conventional Commits message, always `--no-gpg-sign`.
 
 Finish by summarizing the Architectural Anchors and how to start execution with
@@ -141,6 +141,6 @@ Extract before asking: what the user asked for and why, explicit decisions/const
 
 - **You scaffold and design; you do not implement the roadmap.** Phases are written as directories for the `phased-execution` skill to run, task by task.
 - **Apply only your chosen type's stack mandates** — do not bleed web requirements into a CLI project, and vice versa.
-- **Never** create or edit files inside `.agent/PLAN.md`, `AGENTS.md`, or `.agent/phases/complete/` after this skill hands off (the `phase-authoring` skill owns later changes).
+- **Never** create or edit files inside `.agents/PLAN.md`, `AGENTS.md`, or `.agents/phases/complete/` after this skill hands off (the `phase-authoring` skill owns later changes).
 - **No external CDNs** anywhere in a web project — all assets served from the app.
 - Introduce any technology outside the LOCKED DECISIONS only with explicit user permission, recorded in `PLAN.md`.