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-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.
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.
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/socratic-reviewer.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,13 @@ 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; `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.
7
+
Clarify the real question before choosing a direction. Primary workflow surfaces: `reflective-dispatch` for routing; `reflective-research` for multi-voice synthesis; `reflective-handoff-retro` for session transfer.
8
8
9
9
## Scope
10
10
11
11
- In scope: requirements interviews, product direction, technical selection, learning strategy, research question definition.
12
-
- Out of scope: code implementation (`reflective-implement`), production risk gating (`reflective-risk`), source-backed external research (`reflective-research`).
12
+
- Out of scope: code implementation (`reflective-implement`), production risk gating (`reflective-risk`), source-backed external research (`reflective-research`), ticket/spec drafting (`reflective-spec-plan` — use after dispatch when scope is clear).
13
+
- Adjacent: pair with `reflective-brief` when assumptions are still open; dispatch selects strictness before spec or implement work.
Copy file name to clipboardExpand all lines: reflective-prompt-library/01-thinking/why-what-how-done.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
@@ -4,12 +4,13 @@ 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; `reflective-spec-plan` when framing becomes ticket or spec work.
7
+
Gate a task through Why / What / How / Done before choosing strictness or workflow depth. Primary workflow surfaces: `reflective-brief`for pre-commitment gating; `reflective-spec-plan` when framing becomes ticket or spec work.
8
8
9
9
## Scope
10
10
11
11
- In scope: pre-commitment checks on goal, scope, method, and completion evidence for a single task or feature.
12
12
- Out of scope: post-hoc code review (`reflective-review`), handoff retros (`reflective-handoff-retro`), or detailed test implementation.
13
+
- Adjacent: after brief framing, `reflective-dispatch` selects orchestration level before deeper spec or implement 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–81). Not agent instructions — operator checklist.
340
+
Ongoing upkeep after panel close (Rounds 1–82). 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
@@ -354,3 +354,4 @@ Ongoing upkeep after panel close (Rounds 1–81). Not agent instructions — ope
354
354
11. When changing Module Contract subsections on workflow skills, keep `Escalation:` present and run `test_skill_module_contract.py`.
355
355
12. When adding or editing `01-thinking/` lenses, keep `## Human Review` in the preamble (routes to `reflective-risk`) and run `test_thinking_prompts_eval_harness.py`.
356
356
13. When editing workflow skill Escalation bullets, cite only frozen `reflective-*` skills; run `test_skill_module_contract.py` escalation route guard.
357
+
14. When editing `01-thinking/` Purpose preambles, keep `Primary workflow surfaces` aligned exactly with `SKILL_THINKING_SOURCES` via `test_thinking_lens_primary_surfaces_match_consumer_graph`; put escalations and adjacent workflow notes in Scope or Human Review, not on the primary line.
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–81, options A–EP) 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–82, options A–ET) 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.
5.**Doc anti-drift** — `test_routing_contract.py`, cheatsheet parity tests, `test_readme_governance.py`, `test_thinking_prompts_eval_harness.py`, `test_engineering_prompts_eval_harness.py`, `test_prompt_cross_links.py`, `test_core_prompts_eval_harness.py`, `test_agent_prompts_eval_harness.py`, `test_context_prompts_eval_harness.py`, `test_domain_prompts_eval_harness.py`, `test_repo_prompts_eval_harness.py`, `test_validate_governance.py`, `test_validate_links.py`, `test_lint_skills.py`, `test_skill_module_contract.py` (Escalation subsection + Trigger/Methods/Output/Never; 450+ pytest anti-drift suite in CI); reciprocal thinking-lens ↔ skill checks in `test_prompt_cross_links.py`; Human Review + Escalation route-target guards in thinking/skill contract tests
317
+
5.**Doc anti-drift** — `test_routing_contract.py`, cheatsheet parity tests, `test_readme_governance.py`, `test_thinking_prompts_eval_harness.py`, `test_engineering_prompts_eval_harness.py`, `test_prompt_cross_links.py`, `test_core_prompts_eval_harness.py`, `test_agent_prompts_eval_harness.py`, `test_context_prompts_eval_harness.py`, `test_domain_prompts_eval_harness.py`, `test_repo_prompts_eval_harness.py`, `test_validate_governance.py`, `test_validate_links.py`, `test_lint_skills.py`, `test_skill_module_contract.py` (Escalation subsection + Trigger/Methods/Output/Never; 450+ pytest anti-drift suite in CI); reciprocal thinking-lens ↔ skill checks in `test_prompt_cross_links.py` (including strict Primary workflow surfaces parity via `test_thinking_lens_primary_surfaces_match_consumer_graph`); Human Review + Escalation route-target guards in thinking/skill contract tests
318
318
319
319
### Ongoing maintenance (not blockers)
320
320
@@ -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–81; 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–82; 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