You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/counterargument.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Use this to prevent excessive optimism, overengineering, or AI flattery.
4
4
5
5
## Purpose
6
6
7
-
Stress-test optimism, overengineering, and AI flattery before committing resources. Primary workflow surfaces: `reflective-review` and `reflective-minimality`; escalate to `reflective-risk` when trust-boundary or blast-radius signals appear.
7
+
Stress-test optimism, overengineering, and AI flattery before committing resources. Primary workflow surfaces: `reflective-implement` for disputed implementation choices; `reflective-review` and `reflective-minimality` for critique and anti-bloat; escalate to `reflective-risk` when trust-boundary or blast-radius signals appear.
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/critical-thinking-check.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Use this to review articles, strategies, product ideas, technical choices, or AI
4
4
5
5
## Purpose
6
6
7
-
Audit claims, assumptions, and evidence quality before accepting a plan, article, or AI output. Primary workflow surface: `reflective-review`; pair with `reflective-research` when external sources are required.
7
+
Audit claims, assumptions, and evidence quality before accepting a plan, article, or AI output. Primary workflow surfaces: `reflective-review` for diff/plan critique; `reflective-implement` for evidence before material commits; `reflective-risk` for high-blast-radius checks; pair with `reflective-research` when external sources are required.
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/socratic-reviewer.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Suitable for requirements interviews, life decisions, product direction, busines
4
4
5
5
## Purpose
6
6
7
-
Clarify the real question before choosing a direction. Primary workflow surfaces: `reflective-brief` for goal and assumption clarification; escalate to `reflective-spec-plan` when scope is clear enough to plan.
7
+
Clarify the real question before choosing a direction. Primary workflow surfaces: `reflective-brief` for goal and assumption clarification; `reflective-dispatch` for routing; `reflective-research` for multi-voice synthesis; `reflective-handoff-retro` for session transfer; escalate to `reflective-spec-plan` when scope is clear enough to plan.
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/why-what-how-done.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Use this as the core gate prompt before committing to a direction.
4
4
5
5
## Purpose
6
6
7
-
Gate a task through Why / What / How / Done before choosing strictness or workflow depth. Primary workflow surfaces: `reflective-brief` then `reflective-dispatch` for orchestration level selection.
7
+
Gate a task through Why / What / How / Done before choosing strictness or workflow depth. Primary workflow surfaces: `reflective-brief` then `reflective-dispatch` for orchestration level selection; `reflective-spec-plan` when framing becomes ticket or spec work.
Copy file name to clipboardExpand all lines: reflective-prompt-library/GLOSSARY.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -337,7 +337,7 @@ Curated top-of-cheatsheet summary of high-confusion routing traps (ROUTE-002 hol
337
337
338
338
## Governance Maintenance Playbook / 治理維護手冊
339
339
340
-
Ongoing upkeep after panel close (Rounds 1–68). Not agent instructions — operator checklist.
340
+
Ongoing upkeep after panel close (Rounds 1–79). Not agent instructions — operator checklist.
341
341
342
342
**Operational test:** Before router tuning, add fresh ROUTE-002/003 holdout phrases; run `make all`; record decisions in `PROJECT_KNOWLEDGE.md` Decision Index when governance surface changes.
343
343
@@ -350,4 +350,5 @@ Ongoing upkeep after panel close (Rounds 1–68). Not agent instructions — ope
350
350
7. When holdout probe tuples change in `test_validate_route_fixture.py`, mirror cues in EN/zh-TW cheatsheets and run `test_cheatsheet_*_parity.py` (e.g. `test_cheatsheet_dispatch_meta_parity.py`).
351
351
8. Keep `CONTRIBUTING.md` Routing Maintenance aligned with `ROUTING_CONTRACT.md` R8–R12 when boundaries or cheatsheet parity steps change.
352
352
9. When adding benchmark golden tasks, keep `test_benchmark_covers_all_nine_workflows` green and bump `MIN_TASK_COUNT` in `validate_benchmark_fixture.py` if the floor rises.
353
+
10. When changing thinking-lens ↔ skill cross-links, update `SKILL_THINKING_SOURCES` and consumer lists in `01-thinking/` Purpose preambles; run `test_prompt_cross_links.py` (including reciprocal `THINKING_LENS_SKILL_CONSUMERS`).
Copy file name to clipboardExpand all lines: reflective-prompt-library/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Pick **Strictness L1–L6** first (`skills/reflective-dispatch/SKILL.md`, [GLOSS
30
30
31
31
## Governance Panel Record
32
32
33
-
Multi-agent Socratic consensus on project goals and the nine skills (Rounds 1–78, options A–ED) is recorded in [plans/multi-agent-panel-consensus-2026-06-25.md](plans/multi-agent-panel-consensus-2026-06-25.md). Run `make all` before claiming routing or governance changes are verified.
33
+
Multi-agent Socratic consensus on project goals and the nine skills (Rounds 1–79, options A–EH) is recorded in [plans/multi-agent-panel-consensus-2026-06-25.md](plans/multi-agent-panel-consensus-2026-06-25.md). Run `make all` before claiming routing or governance changes are verified.
@@ -384,4 +384,4 @@ Phase 1 quality-gate tooling and documentation are **complete**. Routing consist
384
384
- ✅ Benchmark fixture gate plus optional manual benchmark runs
385
385
- ✅ Research-backed design decisions
386
386
387
-
The project is positioned to grow sustainably with quality discipline built in from the start. **No open implementation blockers** remain from panel Rounds 1–76; work is recurrence-gated maintenance per playbook. The next measurable quality target is **holdout expansion before router tuning** and optional manual baseline-vs-skill benchmark runs — not shipping new core skills without promotion evidence.
387
+
The project is positioned to grow sustainably with quality discipline built in from the start. **No open implementation blockers** remain from panel Rounds 1–79; work is recurrence-gated maintenance per playbook. The next measurable quality target is **holdout expansion before router tuning** and optional manual baseline-vs-skill benchmark runs — not shipping new core skills without promotion evidence.
0 commit comments