agent-method 1.5.12

package/templates/full/CLAUDE.md

@@ -0,0 +1,90 @@
+# {Project Name} — Agent Entry Point
+
+<!-- INSTRUCTION: Replace {Project Name} and write a 1-2 sentence project description below -->
+{Describe what your project does, its architecture, and key technologies.}
+
+## On every query
+
+1. This file is auto-loaded — read it first
+2. Read `STATE.md` for current position, decisions, blockers
+3. Read `.context/PROTOCOL.yaml` for scoping, cascade, and conventions
+4. Scope query against PROTOCOL.yaml `scoping:` section
+5. After work, check PROTOCOL.yaml `close_check` before ending response
+
+## Settings
+
+mode: checkpoint
+<!-- autonomous | checkpoint | collaborative | supervised -->
+<!-- checkpoint: propose plan, wait for approval, report at completion (default) -->
+
+tier: full
+<!-- lite | standard | full -->
+<!-- lite: minimal rules, STATE.md only — for Haiku or simple projects -->
+<!-- standard: core rules + context pairing — for Sonnet (default) -->
+<!-- full: all rules, all intelligence layer files — for Opus or complex projects -->
+
+method_version: 1.6
+<!-- Use `wwa status` to compare against latest -->
+
+## CLI tools (optional)
+
+Install: `npm install -g agent-method` (then use `wwa`), or `pip install wwa-tools`.
+
+| When you want to... | Run |
+|---------------------|-----|
+| Validate this entry point | `wwa check` |
+| See what type of project this is | `wwa scan` |
+| Test how a query routes | `wwa project-discovery` / `wwa context-refresh` / `wwa plan-create` (see CLI docs) |
+| See current plan status | `wwa plan` |
+| Get implementation guidance | `wwa implement` |
+| View project review dashboard | `wwa review` |
+| Show management digest | `wwa digest` |
+| Session close + project snapshot | `wwa close` |
+| Extract a refinement report | `wwa refine` |
+| Extract a case study (with project tokens) | `wwa casestudy` |
+| Check docs coverage | `wwa docs` |
+| Show dependency graph | `wwa deps` |
+| Generate document registry | `wwa doc-review` |
+| Check methodology version | `wwa status` |
+| Update methodology files | `wwa upgrade` |
+| Set up a new project | `wwa init` |
+| Run project discovery workflow | `wwa project-discovery` |
+| Run context refresh workflow | `wwa context-refresh` |
+| Run phase completion workflow | `wwa phase-complete` |
+| Show routing for backlog | `wwa backlog` |
+| Run planning workflow | `wwa plan-create` |
+| Run dependency analysis workflow | `wwa dependency-analysis` |
+| Run debt assessment workflow | `wwa debt-assessment` |
+| Run docs update workflow | `wwa docs-update` |
+| Run cross-reference workflow | `wwa cross-reference` |
+| Append to backlog / decision / finding / session / summary | `wwa add <type> [content]` |
+
+When doing **project review** or **self-review** sessions, use the collection checklist for capture format: `docs/internal/review/collection-checklist.md` (if present).
+
+<!-- INSTRUCTION: The agent can suggest these commands when the user asks about validation,
+     project setup, or methodology updates. All commands auto-detect project type and find
+     entry points automatically. Add --json for machine-readable output. -->
+
+## Do not
+
+- Modify project source code, tests, or pre-existing documentation through methodology operations — only create/modify methodology files (STATE.md, .context/, PLAN.md, etc.)
+- Delete existing project files during brownfield integration — methodology is additive only
+- Load files not in PROTOCOL.yaml scoping read-set for the current query type
+- Defer STATE.md decision recording to end of session
+- Skip cascade checks after file changes
+- Load multiple specialist .context/ files for a single query
+- Record routine queries in STATE.md or SESSION-LOG.md — only decisions, blockers, and high-effort work warrant documentation
+
+<!-- INSTRUCTION: Add project-specific "do not" rules as you discover common mistakes -->
+
+## First session
+
+<!-- AGENT: If PROJECT.md contains {placeholder} text, this is a first session. -->
+Follow the onboarding protocol in `.context/METHODOLOGY.md` — it guides you through
+greenfield (4 stages) or brownfield (5 stages) setup with checkpoints at each step.
+
+## Before ending this response
+
+Read `.context/PROTOCOL.yaml` `close_check`. For each triggered item,
+update the target file now. A response that modifies files but skips
+triggered obligations is incomplete.

package/templates/full/Management/DIGEST.md

@@ -0,0 +1,23 @@
+# Management Digest
+
+<!-- AGENT: Append a row for every HIGH-EFFORT task only.
+     This is the primary management-facing project record — managers and leads
+     read this to understand what significant work happened, without parsing
+     detailed session logs or operational files.
+
+     Low-effort tasks (lookups, status checks, clarifications) are NOT recorded here.
+     See SESSION-LOG.md for complete session data. -->
+
+## What qualifies as high-effort
+
+- Multi-file changes (3+ files)
+- Architectural or design decisions
+- Phase completions
+- Complex queries requiring research or multi-step execution
+- New feature implementations
+
+## Digest
+
+| Date | Task | Query | Outcome | Key Changes | Decisions | Effort | Time |
+|------|------|-------|---------|-------------|-----------|--------|------|
+<!-- Rows added automatically by agent for high-effort tasks -->

package/templates/full/Management/STATUS.md

@@ -0,0 +1,46 @@
+# Project Status
+
+<!-- AGENT: Update this file after significant milestones (phase completions,
+     architectural decisions, blocker changes). This is the management-facing
+     health snapshot — read by leads to understand project state at a glance.
+
+     Do NOT update for routine work. Only update when the project's overall
+     status, direction, or risk profile changes. -->
+
+## Current state
+
+| Field | Value |
+|-------|-------|
+| Phase | {current phase} |
+| Status | {active / blocked / complete} |
+| Active work | {brief description of current task} |
+| Last milestone | {most recent completed phase or significant deliverable} |
+| Next milestone | {what's coming next} |
+
+## Recent decisions
+
+<!-- AGENT: Keep the 5 most recent significant decisions here.
+     Full decision history lives in STATE.md. -->
+
+| Date | Decision | Impact |
+|------|----------|--------|
+<!-- Last 5 significant decisions -->
+
+## Blockers & risks
+
+<!-- AGENT: List active blockers and known risks. Remove when resolved. -->
+
+| Type | Description | Since | Severity |
+|------|-------------|-------|----------|
+<!-- {blocker/risk} | {description} | {date} | {high/medium/low} -->
+
+## Health indicators
+
+<!-- AGENT: Update these after each high-effort task or milestone. -->
+
+| Indicator | Status | Notes |
+|-----------|--------|-------|
+| Scope | {stable / expanding / contracting} | {brief note} |
+| Velocity | {steady / accelerating / slowing} | {brief note} |
+| Technical debt | {low / medium / high} | {brief note} |
+| Context freshness | {current / slightly stale / stale} | {last refresh date} |

package/templates/full/PLAN.md

@@ -0,0 +1,67 @@
+# Current Plan
+
+<!-- INSTRUCTION: This file contains ONE task at a time. Replace the entire
+     contents when starting a new task — never accumulate multiple plans.
+     The agent proposes the plan and waits for human approval before executing. -->
+
+## {Task name}
+
+### Objective
+
+{What this task achieves. One clear sentence.}
+
+### Prerequisites
+
+<!-- INSTRUCTION: What must be true before starting this task? -->
+
+- {Prior phase or task complete}
+- {Required files or context available}
+
+### Dependencies
+
+<!-- INSTRUCTION: What depends on this task? What does this task block? -->
+
+- {Phase/task that depends on this completing}
+
+---
+
+### Step 1: {Step name}
+
+**Objective**: {What this step achieves}
+
+**Read**: {Files to read before this step}
+**Produce**: {Files created or modified by this step}
+
+**Substeps**:
+- a. {First substep}
+- b. {Second substep}
+
+**Verify**: {How to confirm this step is complete and correct}
+
+---
+
+### Step 2: {Step name}
+
+**Objective**: {What this step achieves}
+
+**Read**: {Files to read}
+**Produce**: {Files created or modified}
+
+**Verify**: {Verification criteria}
+
+---
+
+<!-- INSTRUCTION: Add more steps as needed. Each step should have:
+     - Clear objective
+     - Read/produce specs (what files are involved)
+     - Substeps (if complex)
+     - Verification criteria (how to confirm it's done right) -->
+
+### Completion criteria
+
+{Task name} is done when:
+1. {Criterion 1 — specific and measurable}
+2. {Criterion 2}
+3. {Criterion 3}
+
+**Next after {task name}**: {What comes next}

package/templates/full/PROJECT-PROFILE.md

@@ -0,0 +1,61 @@
+# Project Profile
+
+<!-- INSTRUCTION: This file is maintained by the agent. It tracks your project's
+     type, lifecycle stage, and active extensions. The agent reads this to adjust
+     feature priorities and workflow selection. You can also update it manually
+     when your project's situation changes.
+
+     Fill in the initial values during setup. The agent updates lifecycle stage
+     and maturity as the project evolves. -->
+
+## Project identity
+
+- **Types**: [{project-type}]
+- **Extensions**: [{extensions-applied}]
+
+<!-- INSTRUCTION: Project types: code, data, analytical, mixed, general.
+     Extensions: code-project, data-exploration, analytical-system, or none. -->
+
+## Lifecycle
+
+- **Stage**: {stage}
+- **Maturity**: {maturity}
+- **Last transition**: {date} ({from} -> {to})
+
+<!-- INSTRUCTION: Lifecycle stages:
+     - discovery: Understanding an existing project (brownfield entry)
+     - design: Defining architecture and structure (greenfield start)
+     - development: Building and iterating (active implementation)
+     - evolution: Maintaining and extending (stable baseline)
+
+     Maturity levels: new, early, established, legacy.
+     The agent suggests transitions; you decide when to move. -->
+
+## Extension stack
+
+| Extension | Applied | Source |
+|-----------|---------|--------|
+| code-project | {yes/no} | {setup.sh / manual} |
+| data-exploration | {yes/no} | {setup.sh / manual} |
+| analytical-system | {yes/no} | {setup.sh / manual} |
+
+<!-- INSTRUCTION: Track which extensions are active. Extensions can be added
+     mid-project without re-running setup.sh — merge the extension file
+     into your entry point manually and update this table. -->
+
+## Discovery log
+
+<!-- INSTRUCTION: When the agent runs WF-08 (discovery workflow), key findings
+     are recorded here for quick reference. Only used during Discovery stage.
+     Can be deleted once the project moves to Development or Evolution. -->
+
+| Date | Finding | Severity | Action taken |
+|------|---------|----------|-------------|
+
+## Context evolution history
+
+<!-- INSTRUCTION: Track lifecycle transitions and extension changes over time.
+     Helps the agent understand how the project has evolved. -->
+
+| Date | Change | Rationale |
+|------|--------|-----------|

package/templates/full/PROJECT.md

@@ -0,0 +1,80 @@
+# {Your Project Name}
+
+<!-- INSTRUCTION: Replace with a 2-3 sentence description of your project.
+     Include what it does, who it's for, and what technologies it uses. -->
+{Describe what your project does and who it's for}
+
+## Problem
+
+<!-- INSTRUCTION: What problem does this solve? 2-3 bullet points. -->
+
+- {Problem statement 1}
+- {Problem statement 2}
+
+## Solution
+
+<!-- INSTRUCTION: How does the project solve the problem? Brief description of the approach. -->
+
+{Describe your approach}
+
+## Project structure
+
+<!-- INSTRUCTION: Table of top-level directories and their purposes.
+     The agent uses this to understand the project layout.
+     For existing codebases, ask the agent to help populate this from a scan. -->
+
+| Path | Purpose |
+|------|---------|
+| {src/} | {Source code} |
+| {docs/} | {Documentation} |
+
+## Audiences
+
+<!-- INSTRUCTION: Who interacts with this project? Users, developers, managers, agents? -->
+
+| Audience | What they need |
+|----------|---------------|
+| {Developer} | {Working code, clear architecture} |
+| {User} | {Functional product} |
+
+## Principles
+
+<!-- INSTRUCTION: 3-5 guiding principles for decision-making on this project. -->
+
+1. {Principle 1}
+2. {Principle 2}
+3. {Principle 3}
+
+## Agent onboarding
+
+<!-- AGENT: Use these questions to populate this file during the first session.
+     Ask the user each question, draft this file from the answers, and show the
+     draft at the Stage 1 checkpoint before writing. Remove this section after
+     the file is populated — it's scaffolding, not permanent content. -->
+
+### Greenfield (no existing codebase)
+
+Ask the user:
+1. What is your project about? (1-2 sentences for the description above)
+2. Who is it for? (populate the Audiences table)
+3. What problem does it solve? (populate the Problem section)
+4. What technologies, languages, or frameworks will you use? (informs Solution + structure)
+5. What are 2-3 guiding principles for this project? (populate Principles)
+6. What is the top-level directory structure? (populate Project structure table)
+
+### Brownfield (existing codebase)
+
+<!-- AGENT: For brownfield projects, you've already scanned the project at Stage 1.
+     Pre-fill as much as possible from scan results. Only ask what you couldn't determine. -->
+
+Pre-fill from scan:
+- **Description**: infer from README, package.json description, or top-level docs
+- **Project structure**: build from directory listing — auto-populate the table
+- **Technologies**: extract from package.json, requirements.txt, config files, imports
+
+Ask the user only what the scan couldn't determine:
+1. Is this description accurate? (confirm or correct the auto-generated description)
+2. Who is the primary audience? (rarely inferable from code alone)
+3. What problem does this solve from the user's perspective? (intent, not implementation)
+4. What guiding principles drive decisions on this project? (conventions, priorities)
+5. Are there directories I should know about that aren't obvious from the structure? (hidden patterns, legacy areas)

package/templates/full/REQUIREMENTS.md

@@ -0,0 +1,30 @@
+# Requirements
+
+<!-- INSTRUCTION: Define what the project must achieve. Each requirement has an ID,
+     description, phase traceability, and status. Requirements drive the ROADMAP. -->
+
+## Functional requirements
+
+| ID | Requirement | Phase | Status |
+|----|-------------|-------|--------|
+| R1 | {What the system must do} | {Phase #} | pending |
+| R2 | {Second requirement} | {Phase #} | pending |
+| R3 | {Third requirement} | {Phase #} | pending |
+
+<!-- INSTRUCTION: Add requirements as they're identified. Link each to the phase
+     where it will be delivered. Mark "done" when the phase gate passes. -->
+
+## Non-functional requirements
+
+| ID | Requirement | Phase | Status |
+|----|-------------|-------|--------|
+| NF1 | {Performance, security, or usability requirement} | {Phase #} | pending |
+
+## Traceability
+
+<!-- INSTRUCTION: This section maps requirements to deliverables.
+     Update when requirements are completed or deliverables change. -->
+
+| Requirement | Delivered by | Verified by |
+|-------------|-------------|-------------|
+| R1 | {Deliverable name or file} | {How it was verified} |

package/templates/full/ROADMAP.md

@@ -0,0 +1,39 @@
+# Roadmap
+
+<!-- INSTRUCTION: Define phases with deliverables and gate criteria.
+     Each phase should have:
+     - A clear objective (1 sentence)
+     - A deliverable table (what, requirement, status)
+     - A gate (how you know the phase is done)
+     Copy the Phase template below for each phase in your project. -->
+
+## Phase 1 — {Phase name} [status]
+
+<!-- INSTRUCTION: Replace {Phase name} with a descriptive name.
+     Set [status] to one of: current, pending, done -->
+
+{One sentence describing what this phase achieves.}
+
+| Deliverable | Requirement | Status |
+|-------------|-------------|--------|
+| {Deliverable 1} | {Which requirement it satisfies} | pending |
+| {Deliverable 2} | {Which requirement it satisfies} | pending |
+
+**Gate**: {How you know this phase is complete. Be specific — measurable criteria.}
+
+---
+
+## Phase 2 — {Phase name} [pending]
+
+{One sentence describing what this phase achieves.}
+
+| Deliverable | Requirement | Status |
+|-------------|-------------|--------|
+| {Deliverable 1} | {Requirement} | pending |
+
+**Gate**: {Completion criteria}
+
+---
+
+<!-- INSTRUCTION: Add more phases as needed. Each phase should be achievable
+     in 1-5 sessions. If a phase takes longer, split it. -->

package/templates/full/Reviews/INDEX.md

@@ -0,0 +1,41 @@
+# Project Reviews
+
+<!-- AGENT: This is the review dashboard — a synthesized view of project intelligence.
+     Update the summary table when corresponding source files change significantly.
+     Each area links to a dedicated drill-down file for detailed analysis.
+
+     Source files: ROADMAP.md, PLAN.md, PROJECT.md, REQUIREMENTS.md, STATE.md, todos/backlog.md
+     This file stays lean — detail lives in the drill-down files. -->
+
+## At a glance
+
+| Area | Status | Last updated | Drill-down |
+|------|--------|-------------|------------|
+| Roadmap | {on track / behind / ahead} | {date} | [roadmap.md](roadmap.md) |
+| Plan | {active / blocked / between tasks} | {date} | [plan.md](plan.md) |
+| Project | {healthy / needs attention} | {date} | [project.md](project.md) |
+| Requirements | {N/M covered} | {date} | [requirements.md](requirements.md) |
+| State | {N decisions, N blockers, N open Qs} | {date} | [state.md](state.md) |
+| Backlog | {N items, N categories} | {date} | [backlog.md](backlog.md) |
+
+## Key metrics
+
+<!-- AGENT: Populate from source files. Update after milestones. -->
+
+- **Phases completed**: {N of M}
+- **Requirements covered**: {N of M} ({percentage}%)
+- **Active blockers**: {count}
+- **Open questions**: {count}
+- **Backlog items**: {count}
+- **Decisions recorded**: {count}
+
+## Trend indicators
+
+<!-- AGENT: Track how metrics change over time. Update after phase completions. -->
+
+| Metric | Previous | Current | Trend |
+|--------|----------|---------|-------|
+| Phases completed | {N} | {N} | {↑ / → / ↓} |
+| Requirements coverage | {N}% | {N}% | {↑ / → / ↓} |
+| Open blockers | {N} | {N} | {↑ / → / ↓} |
+| Backlog size | {N} | {N} | {↑ / → / ↓} |

package/templates/full/Reviews/backlog.md

@@ -0,0 +1,52 @@
+# Backlog Review
+
+<!-- AGENT: Synthesize from todos/backlog.md. Track backlog health — item counts,
+     categories, aging, completion rates. This helps identify neglected areas
+     and prioritization patterns.
+     Update after significant backlog changes (new categories, large batch completions).
+
+     Source: todos/backlog.md
+     Parent: Reviews/INDEX.md (update "At a glance" row when this changes) -->
+
+## Summary
+
+- **Total items**: {count}
+- **Completed**: {count} ({%})
+- **Pending**: {count} ({%})
+
+## By category
+
+| Category | Total | Done | Pending | Completion |
+|----------|-------|------|---------|------------|
+<!-- Group backlog items by their section headings -->
+
+## Aging analysis
+
+<!-- AGENT: How long have pending items been in the backlog? Any items that should
+     be promoted to the roadmap or removed? -->
+
+| Age bracket | Count |
+|-------------|-------|
+| Added this phase | {N} |
+| 1-2 phases old | {N} |
+| 3+ phases old | {N} |
+
+### Stale items
+
+<!-- Items that have been pending for 3+ phases. Should they be promoted, deferred, or removed? -->
+
+## Prioritization patterns
+
+<!-- AGENT: What gets completed first? Any categories consistently neglected? -->
+
+### Fast-tracked categories
+
+<!-- Categories with high completion rates — what gets done quickly? -->
+
+### Neglected categories
+
+<!-- Categories with low completion rates — what gets deferred repeatedly? -->
+
+## Recommendations
+
+<!-- AGENT: Based on backlog analysis, what should be prioritized next? -->

package/templates/full/Reviews/plan.md

@@ -0,0 +1,43 @@
+# Plan Review
+
+<!-- AGENT: Synthesize from PLAN.md. Track plan execution patterns — how well do plans
+     match actual outcomes? What patterns emerge in task sizing and completion?
+     Update after each plan completes or when plan structure changes.
+
+     Source: PLAN.md (current), SUMMARY.md (historical)
+     Parent: Reviews/INDEX.md (update "At a glance" row when this changes) -->
+
+## Current plan status
+
+| Field | Value |
+|-------|-------|
+| Plan | {current plan name/phase} |
+| Steps | {completed}/{total} |
+| Status | {in progress / blocked / complete} |
+| Started | {date} |
+
+## Execution history
+
+<!-- AGENT: Track completed plans. Populate from SUMMARY.md audit trail. -->
+
+| Plan | Steps | Outcome | Duration | Revisions |
+|------|-------|---------|----------|-----------|
+<!-- {plan name} | {N steps} | {completed / partial / abandoned} | {time} | {count} -->
+
+## Execution patterns
+
+<!-- AGENT: What patterns emerge across plan completions? -->
+
+### Task sizing accuracy
+
+- **Plans completed as designed**: {count} ({%})
+- **Plans that needed scope adjustment**: {count} ({%})
+- **Plans abandoned/rewritten**: {count} ({%})
+
+### Common revision triggers
+
+<!-- What causes plans to be revised? -->
+
+### Step completion patterns
+
+<!-- Do certain types of steps take longer or fail more often? -->

package/templates/full/Reviews/project.md

@@ -0,0 +1,41 @@
+# Project Review
+
+<!-- AGENT: Synthesize from PROJECT.md and PROJECT-PROFILE.md. Track how the project
+     vision, scope, and principles evolve over time. Update after significant scope
+     changes, audience shifts, or principle revisions.
+
+     Source: PROJECT.md, PROJECT-PROFILE.md
+     Parent: Reviews/INDEX.md (update "At a glance" row when this changes) -->
+
+## Project identity
+
+| Field | Current value |
+|-------|--------------|
+| Name | {from PROJECT.md} |
+| Type | {from PROJECT-PROFILE.md} |
+| Lifecycle stage | {from PROJECT-PROFILE.md} |
+| Active extensions | {from PROJECT-PROFILE.md} |
+
+## Scope evolution
+
+<!-- AGENT: Track how project scope has changed. Has it grown, contracted, or shifted? -->
+
+| Date | Change | Type | Impact |
+|------|--------|------|--------|
+<!-- {date} | {what changed} | {expansion / contraction / pivot} | {brief impact} -->
+
+## Principle adherence
+
+<!-- AGENT: Review PROJECT.md principles. Are they being followed in practice? -->
+
+| Principle | Status | Evidence |
+|-----------|--------|----------|
+<!-- {principle from PROJECT.md} | {followed / at risk / violated} | {brief evidence} -->
+
+## Audience alignment
+
+<!-- AGENT: Are we building for the right audience? Any shifts in who uses this? -->
+
+## Technology health
+
+<!-- AGENT: Are technology choices from PROJECT.md still appropriate? Any concerns? -->

package/templates/full/Reviews/requirements.md

@@ -0,0 +1,42 @@
+# Requirements Review
+
+<!-- AGENT: Synthesize from REQUIREMENTS.md. Track requirements coverage, completion
+     status, and traceability to roadmap phases. Update after requirement changes
+     or phase completions that satisfy requirements.
+
+     Source: REQUIREMENTS.md, ROADMAP.md (phase mapping)
+     Parent: Reviews/INDEX.md (update "At a glance" row when this changes) -->
+
+## Coverage summary
+
+| Status | Count | Percentage |
+|--------|-------|------------|
+| Done | {N} | {%} |
+| In progress | {N} | {%} |
+| Pending | {N} | {%} |
+| Deferred | {N} | {%} |
+| **Total** | {N} | 100% |
+
+## Traceability matrix
+
+<!-- AGENT: Map requirements to roadmap phases. Which phases satisfy which requirements? -->
+
+| Requirement | Description | Phase | Status |
+|-------------|-------------|-------|--------|
+<!-- {R-ID} | {brief description} | {phase} | {done / in progress / pending} -->
+
+## Coverage gaps
+
+<!-- AGENT: Are there requirements with no clear path to completion? -->
+
+| Requirement | Gap description | Risk |
+|-------------|----------------|------|
+<!-- Requirements not yet mapped to a phase or at risk of being unmet -->
+
+## Change history
+
+<!-- AGENT: Track when requirements are added, modified, or removed. -->
+
+| Date | Requirement | Change | Rationale |
+|------|-------------|--------|-----------|
+<!-- {date} | {R-ID} | {added / modified / removed} | {why} -->