From 26dd92581cd0a85a28f4bceb43dc1f17e8c4a1c8 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Sun, 5 Jul 2026 14:14:04 -0400 Subject: [PATCH] conductor(workflow): add Session Start Checklist items 1-13 (spec-first mandatory is item 13) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per HIGH-priority recommendation #1 from superpowers_review_20260619/decisions.md. The Session Start Checklist section previously had the header but no items (per superpowers_review §2.4 the section was referenced everywhere as a 12-item list but no items appeared in workflow.md). This commit backfills the canonical 12-item list (per superpowers_review §2.2 and AGENTS.md) AND adds item 13 making the spec-first discipline explicit for ad-hoc edits (per the brainstorming skill's HARD-GATE). Refs: - superpowers_review_20260619/report.md §2 (PARTIAL+INTEGRATE-PARTIAL) - superpowers_review_20260619/decisions.md #1 (HIGH-priority) - conductor/tracks/superpowers_review_apply_high_20260705/spec.md §3.1 --- conductor/workflow.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/conductor/workflow.md b/conductor/workflow.md index 39821ae7..8dd5ef85 100644 --- a/conductor/workflow.md +++ b/conductor/workflow.md @@ -2,6 +2,22 @@ ## Session Start Checklist (MANDATORY) +Before any work in this repository, complete the following checks. **BLOCK PROGRESS** until all checklist items are confirmed. + +1. Read `AGENTS.md` (the project's top-level agent-facing rules; "Critical Anti-Patterns" section is HARD BANs). +2. Read `conductor/workflow.md` (this file) — especially §"Code Style (MANDATORY - Python)", §"Tier 1 Track Initialization Rules", §"Task Workflow". +3. Read `conductor/tech-stack.md` — to confirm the tech stack has not changed. +4. Read `conductor/product.md` and `conductor/product-guidelines.md` — for product context and Core Value discipline. +5. Check `conductor/tracks.md` for active tracks; check `conductor/chronology.md` for shipped history. +6. Read the relevant `conductor/code_styleguides/data_oriented_design.md` (DOD + Python Type Promotion Mandate). +7. Read the relevant `conductor/code_styleguides/python.md` (1-space indentation; Result[T] discipline). +8. Read the relevant `conductor/code_styleguides/type_aliases.md` (per aggregate-file TypeAlias conventions). +9. Read the relevant `conductor/code_styleguides/error_handling.md` (Result[T] + NIL_T sentinel pattern). +10. Read the relevant `docs/guide_*.md` for the area you're working in (e.g., `guide_architecture.md`, `guide_ai_client.md`, `guide_mcp_client.md`). +11. AST Skeleton summaries of: `./src`, `./simulation`, `./tests`, `./scripts` python files (use `manual-slop_py_get_code_outline` or `manual-slop_py_get_skeleton`). +12. Activate the `mma-orchestrator` skill (or the appropriate tier-1/tier-2 skill per role) via the Skill tool. +13. **Spec-first is mandatory for any creative work.** Before writing any code, scaffolding any project, or taking any implementation action for a new feature, fix, or refactor, you MUST have an approved spec (`conductor/tracks//spec.md`) and plan (`conductor/tracks//plan.md`) per §"Planning Session Workflow". Ad-hoc edits (single-line fixes, comment updates, formatting) are exempt; anything that touches 3+ files or adds new behavior requires a spec. Per `conductor/tracks/superpowers_review_20260619/report.md` §2 (PARTIAL+INTEGRATE-PARTIAL verdict for the brainstorming skill). + ## Code Style (MANDATORY - Python) - **1-space indentation** for ALL Python code (NO EXCEPTIONS)