feat: add methodology artifact type with consumption mechanisms (#1488) (#1609)

* test(#1488): add failing tests for methodology artifact type

- Test artifact-types.md exists with methodology type documented
- Test shape, lifecycle, location fields are present
- Test discuss-phase-assumptions.md consumes METHODOLOGY.md
- Test pause-work.md Required Reading includes METHODOLOGY.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* feat(#1488): add methodology artifact type with consumption mechanisms

- Create get-shit-done/references/artifact-types.md documenting all GSD
  artifact types including the new methodology type
- Methodology artifact: standing reference of named interpretive lenses,
  located at .planning/METHODOLOGY.md, lifecycle Created → Active → Superseded
- Add load_methodology step to discuss-phase-assumptions.md so active lenses
  are read before assumption analysis and applied to surfaced findings
- Add METHODOLOGY.md to pause-work.md Required Reading template so resuming
  agents inherit the project's analytical orientation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
2026-04-03 13:06:10 -04:00
committed by GitHub
parent 3078279a9a
commit bdf6b5efcb
4 changed files with 269 additions and 0 deletions

View File

@@ -186,6 +186,24 @@ Parse JSON for: `todo_count`, `matches[]`.
**Auto mode (`--auto`):** Fold all todos with score >= 0.4 automatically. Log the selection.
</step>
<step name="load_methodology">
Read the project-level methodology file if it exists. This must happen before assumption analysis
so that active lenses shape how assumptions are generated and evaluated.
```bash
cat .planning/METHODOLOGY.md 2>/dev/null || true
```
**If METHODOLOGY.md exists:**
- Parse each named lens: its diagnoses, recommendations, and triggering conditions
- Store as internal `<active_lenses>` for use in deep_codebase_analysis and present_assumptions
- When spawning the gsd-assumptions-analyzer, pass the lens list so it can flag which lenses apply
- When presenting assumptions, append a "Methodology" section showing which lenses were applied
and what they flagged (if anything)
**If METHODOLOGY.md does not exist:** Skip silently. This artifact is optional.
</step>
<step name="scout_codebase">
Lightweight scan of existing code to inform assumption generation.

View File

@@ -142,6 +142,7 @@ last_updated: [timestamp from current-timestamp]
## Required Reading (in order)
<!-- List documents the resuming agent must read before acting -->
1. [document] — [why it matters]
1. `.planning/METHODOLOGY.md` (if it exists) — project analytical lenses; apply before any assumption analysis
## Critical Anti-Patterns (do NOT repeat these)
<!-- Mistakes discovered this session that must be structurally avoided -->