superlab 0.1.1 → 0.1.3

package/package-assets/codex/prompts/lab-spec.md

@@ -1,5 +1,5 @@
 ---
-description: Convert an approved idea into OpenSpec spec-driven artifacts
+description: Convert an approved idea into a lab change directory
 argument-hint: approved idea context
 ---
 

package/package-assets/shared/changes/README.md

@@ -0,0 +1,10 @@
+# `.superlab/changes`
+
+Each approved `/lab:spec` change lives in one directory:
+
+- `.superlab/changes/<change-id>/proposal.md`
+- `.superlab/changes/<change-id>/design.md`
+- `.superlab/changes/<change-id>/spec.md`
+- `.superlab/changes/<change-id>/tasks.md`
+
+This keeps spec artifacts grouped under `lab` instead of depending on external directory conventions.

package/package-assets/shared/config/workflow.json

@@ -0,0 +1,5 @@
+{
+  "workflow_language": "en",
+  "paper_language": "en",
+  "paper_format": "latex"
+}

package/package-assets/shared/context/decisions.md

@@ -0,0 +1,11 @@
+# Decision Log
+
+Record stable decisions that later stages should not silently overturn.
+
+## Decisions
+
+1. Decision:
+   Reason:
+   Stage:
+   Evidence:
+   Revisit trigger:

package/package-assets/shared/context/evidence-index.md

@@ -0,0 +1,16 @@
+# Evidence Index
+
+Map every important claim to concrete artifacts.
+
+## Claims
+
+1. Claim:
+   Supporting artifacts:
+   Metrics:
+   Limits or caveats:
+
+## Rejected Claims
+
+1. Claim:
+   Why it was weakened or removed:
+   Artifact showing the failure:

package/package-assets/shared/context/mission.md

@@ -0,0 +1,27 @@
+# Research Mission
+
+## Core Problem
+
+- One-sentence problem:
+- Why it matters:
+- Target failure case:
+
+## Success Criteria
+
+- Primary metric:
+- Success threshold:
+- Required baselines:
+- Minimum evidence needed:
+
+## Frozen Boundaries
+
+- Dataset or benchmark scope:
+- Split policy:
+- Evaluation protocol:
+- Hard constraints:
+
+## Campaign Status
+
+- Approved direction:
+- Current owner or session:
+- Last stage that updated this mission:

package/package-assets/shared/context/open-questions.md

@@ -0,0 +1,11 @@
+# Open Questions
+
+Track unresolved issues so the workflow does not invent answers silently.
+
+## Active Questions
+
+1. Question:
+   Why it matters:
+   Best current options:
+   Resolution owner:
+   Target stage:

package/package-assets/shared/context/state.md

@@ -0,0 +1,19 @@
+# Workflow State
+
+## Current Stage
+
+- Active stage:
+- Current objective:
+- Next required output:
+
+## Latest Update
+
+- Last completed action:
+- Latest artifact path:
+- Latest run or report id:
+
+## Next Step
+
+- Immediate next action:
+- Blocking issue:
+- Human decision needed:

package/package-assets/shared/examples/minimal-uplift-workflow.md

@@ -20,10 +20,10 @@ Use `/lab:spec` after approving the idea artifact.
 
 Expected artifacts:
 
-- `proposal.md`
-- `design.md`
-- `specs/<capability>/spec.md`
-- `tasks.md`
+- `.superlab/changes/<change-id>/proposal.md`
+- `.superlab/changes/<change-id>/design.md`
+- `.superlab/changes/<change-id>/spec.md`
+- `.superlab/changes/<change-id>/tasks.md`
 
 ## 3. Run
 

package/package-assets/shared/skills/lab/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lab
-description: Strict research workflow for idea development, OpenSpec specification, small-scale experiment execution, bounded iteration, reviewer-grade critique, final reporting, and paper-writing.
+description: Strict research workflow for idea development, lab change specification, small-scale experiment execution, bounded iteration, reviewer-grade critique, final reporting, and paper-writing.
 ---
 
 # /lab Skill
@@ -9,10 +9,18 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 
 ## Global Rules
 
-- Treat OpenSpec CLI as required from `/lab:spec` onward.
 - Keep idea generation, specification, execution, review, and reporting as separate stages.
 - Keep paper writing separate from experiment execution and reporting.
+- Start each stage with a concise user-facing summary before writing artifacts.
+- After that summary, decide whether immediate artifact creation is useful; if yes, write the artifact and then report the output path plus next step.
+- When a missing assumption would materially change the stage outcome, ask one clarifying question at a time.
+- When there are multiple viable paths, present 2-3 approaches with trade-offs and a recommendation before converging.
+- When a stage materially sets downstream direction, keep an explicit approval gate before proceeding.
 - Write durable artifacts to disk instead of leaving key decisions only in chat.
+- Use `.superlab/config/workflow.json` as the global contract for workflow language, paper language, and paper format.
+- Use `.superlab/context/`` as the shared project state for both Codex and Claude entrypoints.
+- Workflow artifacts should follow the installed workflow language.
+- Final paper output should default to LaTeX, and its manuscript language should be decided separately from the workflow language.
 - Separate sourced facts from model-generated hypotheses.
 - Preserve failed runs, failed ideas, and limitations.
 
@@ -21,6 +29,8 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 ### `/lab:idea`
 
 - Search relevant literature, baselines, datasets, and evaluation metrics before proposing a plan.
+- Read `.superlab/context/`mission.md` and `.superlab/context/`open-questions.md` before drafting.
+- Ask one clarifying question at a time when critical ambiguity remains.
 - State the problem, the failure case, and why the problem matters before proposing solutions.
 - Classify the idea by contribution category and breakthrough level.
 - Compare against existing methods explicitly and state why the idea should be better.
@@ -30,24 +40,26 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Critique the idea before converging on it.
 - Keep an explicit approval gate before `/lab:spec`.
 - Write idea artifacts with the template in `.superlab/templates/idea.md`.
+- Update `.superlab/context/`mission.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`open-questions.md` after convergence.
 - Do not implement code in this stage.
 
 ### `/lab:spec`
 
-- Require `bash scripts/check_openspec.sh`.
-- Use OpenSpec CLI as the execution path, not just as naming inspiration:
-  - initialize OpenSpec if the project is not initialized yet
-  - identify or create the active change
-  - use `openspec-cn instructions`, `openspec-cn status`, and `openspec-cn validate` while drafting and applying the spec
-- Convert the approved idea into OpenSpec `spec-driven` artifacts using `.superlab/templates/proposal.md`, `.superlab/templates/design.md`, `.superlab/templates/spec.md`, and `.superlab/templates/tasks.md`.
+- Read `.superlab/config/workflow.json` before drafting the change.
+- Read `.superlab/context/`mission.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`state.md` before drafting the change.
+- Use `.superlab/changes/<change-id>/` as the canonical lab change directory.
+- Convert the approved idea into lab change artifacts using `.superlab/templates/proposal.md`, `.superlab/templates/design.md`, `.superlab/templates/spec.md`, and `.superlab/templates/tasks.md`.
+- Update `.superlab/context/`state.md` and `.superlab/context/`decisions.md` after freezing the spec.
 - Do not skip task definition.
 
 ### `/lab:run`
 
 - Start with the smallest meaningful experiment.
+- Read `.superlab/context/`mission.md` and `.superlab/context/`state.md` before choosing the run.
 - Register the run with `.superlab/scripts/register_run.py`.
 - Normalize the result with `.superlab/scripts/eval_report.py`.
 - Validate normalized output with `.superlab/scripts/validate_results.py`.
+- Update `.superlab/context/`state.md` and `.superlab/context/`evidence-index.md` after the run.
 
 ### `/lab:iterate`
 
@@ -61,29 +73,40 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
   - maximum iteration count
 - Only change implementation hypotheses within the loop.
 - Require a normalized evaluation report each round.
+- Read `.superlab/context/`mission.md`, `.superlab/context/`state.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`evidence-index.md` at the start of each round.
 - Switch to diagnostic mode if risk increases for two consecutive rounds.
 - Write round reports with `.superlab/templates/iteration-report.md`.
+- Update `.superlab/context/`state.md`, `.superlab/context/`decisions.md`, `.superlab/context/`evidence-index.md`, and `.superlab/context/`open-questions.md` each round as needed.
 - Stop at threshold success or iteration cap, and record blockers plus next-best actions when the campaign ends without success.
 
 ### `/lab:review`
 
 - Work in reviewer mode, not implementation mode.
+- Read `.superlab/context/`mission.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`evidence-index.md` before reviewing.
+- Start with a concise summary of what is being reviewed and the top review question.
 - Prioritize methodology, fairness, leakage, statistics, ablations, and claim discipline.
+- Output findings first, then fatal flaws, then fix priority, then residual risks.
 - Use `.superlab/templates/review-checklist.md`.
+- Write durable review conclusions back to `.superlab/context/`state.md` or `.superlab/context/`open-questions.md` when they affect later stages.
 
 ### `/lab:report`
 
 - Summarize all validated iteration summaries.
+- Read `.superlab/context/`mission.md`, `.superlab/context/`state.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`evidence-index.md` before drafting.
 - Aggregate them with `.superlab/scripts/summarize_iterations.py`.
 - Write the final document with `.superlab/templates/final-report.md`.
 - Keep failed attempts and limitations visible.
+- Update `.superlab/context/`state.md` and `.superlab/context/`evidence-index.md` with report-level handoff notes.
 
 ### `/lab:write`
 
 - Start only after `report` artifacts are stable enough to support paper claims.
+- Read `.superlab/config/workflow.json` before drafting and enforce its `paper_language` and `paper_format`.
+- Read `.superlab/context/`mission.md`, `.superlab/context/`decisions.md`, and `.superlab/context/`evidence-index.md` before drafting.
 - Write one paper section or one explicit subproblem per round.
 - Bind each claim to evidence from `report`, iteration reports, or normalized summaries.
-- Write paper artifacts with `.superlab/templates/paper-plan.md`, `.superlab/templates/paper-section.md`, and `.superlab/templates/write-iteration.md`.
+- Write planning artifacts with `.superlab/templates/paper-plan.md`, `.superlab/templates/paper-section.md`, and `.superlab/templates/write-iteration.md`.
+- Write final manuscript artifacts with `.superlab/templates/paper.tex` and `.superlab/templates/paper-section.tex`.
 - Use the vendored paper-writing references under `skills/lab/references/paper-writing/`.
 - Load only the current section guide, plus `paper-review.md` and `does-my-writing-flow-source.md`.
 - Build a compact mini-outline before prose.
@@ -93,17 +116,19 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Before finalizing a round, append and answer the five-dimension self-review checklist and revise unresolved items.
 - Apply paper-writing discipline without changing experimental truth.
 - If the evidence is insufficient, stop and route back to `review` or `iterate`.
+- Update `.superlab/context/`state.md` and `.superlab/context/`evidence-index.md` when section-level claim status changes.
 
 ## Hard Gates
 
 - No implementation before `/lab:spec`.
 - No unconstrained iteration. Every `/lab:iterate` campaign must declare done criteria and `max_iterations`.
 - No final report without validated normalized results.
-- No paper-writing round without stable report artifacts and evidence links.
+- No paper-writing round without stable report artifacts, evidence links, and LaTeX manuscript output.
 
 ## References
 
 - Workflow summary: `.codex/skills/lab/references/workflow.md` or `.claude/skills/lab/references/workflow.md`
+- Brainstorming integration: `.codex/skills/lab/references/brainstorming-integration.md` or `.claude/skills/lab/references/brainstorming-integration.md`
 - Idea stage guide: `.codex/skills/lab/stages/idea.md` or `.claude/skills/lab/stages/idea.md`
 - Spec stage guide: `.codex/skills/lab/stages/spec.md` or `.claude/skills/lab/stages/spec.md`
 - Run stage guide: `.codex/skills/lab/stages/run.md` or `.claude/skills/lab/stages/run.md`
@@ -114,5 +139,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Paper-writing integration: `.codex/skills/lab/references/paper-writing-integration.md` or `.claude/skills/lab/references/paper-writing-integration.md`
 - Vendored paper-writing references: `.codex/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md` or `.claude/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md`
 - Command adapters: the installed `/lab:*` command assets
+- Shared workflow config: `.superlab/config/workflow.json`
+- Shared project context: `.superlab/context/`{mission,state,decisions,evidence-index,open-questions}.md`
 - Templates: `.superlab/templates/`
 - Scripts: `.superlab/scripts/`

package/package-assets/shared/skills/lab/references/brainstorming-integration.md

@@ -0,0 +1,21 @@
+# Brainstorming Integration for `/lab`
+
+This reference keeps brainstorming-style interaction rules centralized so each `/lab` stage can stay small and stage-specific.
+
+## Shared Rules
+
+- Start with a concise user-facing summary before creating or revising artifacts.
+- If a missing assumption would materially change the stage outcome, ask one clarifying question at a time.
+- If multiple viable directions exist, present 2-3 approaches with trade-offs and a recommendation before converging.
+- Keep an explicit approval gate when the stage commits downstream direction or locks in scope.
+- Prefer thin stage-specific contracts over copying the full brainstorming workflow into every stage guide.
+
+## Stage Adaptation
+
+- `idea`: use the full pattern most strongly because ambiguity and design exploration are highest here.
+- `spec`: compare viable change decomposition or validation plans before freezing the lab change directory.
+- `run`: compare the smallest meaningful experiment options before spending compute.
+- `iterate`: compare the next 2-3 hypotheses when there is more than one defensible next move.
+- `review`: clarify review scope only when ambiguity changes findings, then stay in reviewer mode.
+- `report`: compare report framing options only when they change interpretation or reader takeaway.
+- `write`: compare section-level narrative structures only when more than one structure is defensible.

package/package-assets/shared/skills/lab/references/workflow.md

@@ -25,7 +25,7 @@ Escalate to a higher-level redesign instead of mutating the mission when the cur
 ## Required Artifacts
 
 - `docs/lab/idea.md`
-- OpenSpec `proposal`, `design`, `spec`, `tasks`
+- one lab change directory under `.superlab/changes/<change-id>/`
 - normalized JSON summary from `scripts/eval_report.py`
 - per-round report in `docs/lab/iterations/`
 - final report in `docs/lab/report.md`

package/package-assets/shared/skills/lab/stages/idea.md

@@ -24,6 +24,19 @@
 - Mark sourced facts clearly.
 - Mark generated hypotheses clearly.
 - Do not merge them into one undifferentiated summary.
+- Ask one clarifying question at a time when a missing assumption would materially change the proposal.
+- Before writing the full artifact, give the user a short summary with the one-sentence problem, why current methods fail, and the three meaningful points.
+
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/open-questions.md`
+
+## Context Write Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/open-questions.md`
 
 ## Recommended Structure
 

package/package-assets/shared/skills/lab/stages/iterate.md

@@ -12,6 +12,20 @@ Declare and keep fixed:
 - completion_promise
 - maximum iteration count
 
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/state.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/evidence-index.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/evidence-index.md`
+- `.superlab/context/open-questions.md`
+
 ## Per-Round Output
 
 - round hypothesis
@@ -35,3 +49,10 @@ If the loop stops without success, record:
 - what failed
 - top 3 blockers
 - next best actions
+
+## Interaction Contract
+
+- Start each round with a concise summary of current status, the leading hypothesis, and the main round risk.
+- If the next move depends on an unresolved assumption, ask one clarifying question at a time.
+- If more than one next hypothesis is credible, present 2-3 approaches with trade-offs and recommend the next bounded experiment before changing the mission state.
+- Keep an approval gate when a proposed change would alter the frozen mission instead of only changing the implementation hypothesis.

package/package-assets/shared/skills/lab/stages/report.md

@@ -10,9 +10,28 @@
 - limitations
 - next steps
 
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/state.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/evidence-index.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/evidence-index.md`
+
 ## Evidence Rules
 
 - Do not hide failed iterations.
 - Tie every major claim to recorded summaries or iteration artifacts.
 - Prefer conservative interpretation over marketing language.
 - Leave a clear handoff path into `/lab:write` with evidence links that section drafts can cite.
+
+## Interaction Contract
+
+- Start with a concise summary of the campaign outcome, strongest supported claim, and biggest reporting risk.
+- If a missing assumption would change report interpretation, ask one clarifying question at a time.
+- If there are multiple defensible report framings, present 2-3 approaches with trade-offs and recommend the most evidence-faithful framing before writing.
+- Keep an approval gate when the reporting frame would materially affect what the paper later claims.

package/package-assets/shared/skills/lab/stages/review.md

@@ -1,5 +1,25 @@
 # `/lab:review` Stage Guide
 
+## Required Flow
+
+1. Give a concise summary of the artifact or result under review.
+2. State the top review question or risk focus.
+3. Audit in reviewer mode.
+4. Output fatal flaws first when present.
+5. Rank the fix priority.
+6. End with residual risks and a clear next action.
+
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/evidence-index.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/open-questions.md`
+
 ## Reviewer Priorities
 
 - unfair or weak baselines
@@ -11,6 +31,16 @@
 
 ## Output Style
 
+- concise summary first
 - findings first
+- fatal flaws called out explicitly
+- fix priority stated clearly
 - evidence-linked critique
 - explicit residual risks
+
+## Interaction Contract
+
+- Start with a concise summary of the review target and the main reviewer question.
+- Ask one clarifying question at a time only if review scope ambiguity would change findings or severity.
+- If there are multiple legitimate review framings, present 2-3 approaches with trade-offs and recommend the strictest useful framing.
+- Do not use brainstorming to soften critique; once scope is clear, stay in reviewer mode and deliver findings directly.

package/package-assets/shared/skills/lab/stages/run.md

@@ -7,6 +7,16 @@
 - normalized evaluation summary
 - validation result for the normalized summary
 
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/state.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/evidence-index.md`
+
 ## Constraints
 
 - Prefer the smallest experiment that exercises the full pipeline.
@@ -20,3 +30,10 @@
 3. Execute the smallest useful experiment
 4. Normalize raw metrics
 5. Validate the normalized summary
+
+## Interaction Contract
+
+- Start with a concise summary of the run goal, smallest candidate experiment, and primary execution risk.
+- If the next run depends on an unresolved assumption, ask one clarifying question at a time.
+- If there are multiple defensible tiny-run options, present 2-3 approaches with trade-offs and recommend the cheapest informative run.
+- Only ask for approval when choosing a run path would materially spend more time or compute than the default smallest experiment.

package/package-assets/shared/skills/lab/stages/spec.md

@@ -2,21 +2,33 @@
 
 ## Required Output
 
-- an active OpenSpec change id
-- OpenSpec `proposal`
-- OpenSpec `design`
-- OpenSpec `spec`
-- OpenSpec `tasks`
-
-## Required CLI Flow
-
-1. Verify OpenSpec is installed with `bash scripts/check_openspec.sh`.
-2. If the project is not initialized, run `openspec-cn init`.
-3. Identify the active change with `openspec-cn list --json` or create/select one before drafting.
-4. Pull the schema-aware instructions with `openspec-cn instructions --change <change-id>` or `.superlab/scripts/openspec_change.sh instructions <artifact> <change-id>`.
-5. Draft proposal, design, spec delta, and tasks for that change.
-6. Check completion state with `openspec-cn status --change <change-id>` or `.superlab/scripts/openspec_change.sh status <change-id>`.
-7. Validate the change with `openspec-cn validate <change-id>` or `.superlab/scripts/openspec_change.sh validate <change-id>`.
+- a lab change id
+- `.superlab/changes/<change-id>/proposal.md`
+- `.superlab/changes/<change-id>/design.md`
+- `.superlab/changes/<change-id>/spec.md`
+- `.superlab/changes/<change-id>/tasks.md`
+
+## Config Read Set
+
+- `.superlab/config/workflow.json`
+
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/state.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/decisions.md`
+
+## Required Change Layout
+
+1. Identify or create a lab change id.
+2. Create `.superlab/changes/<change-id>/`.
+3. Draft `proposal.md`, `design.md`, `spec.md`, and `tasks.md` inside that directory.
+4. Keep the change self-contained so downstream stages can read one directory and its linked context.
 
 ## Conversion Rules
 
@@ -24,11 +36,18 @@
 - Preserve evaluation boundaries from the idea stage.
 - Translate risks into concrete tasks when possible.
 - Make task granularity small enough that `/lab:run` and `/lab:iterate` can execute predictably.
-- Do not treat OpenSpec as file naming only. The change id, CLI instructions, status, and validation are part of the stage contract.
+- Use one lab-native change directory per approved idea instead of scattering spec artifacts.
+
+## Interaction Contract
+
+- Start with a concise summary of the approved idea, target change, and the main spec risk.
+- If change decomposition or validation strategy is materially ambiguous, ask one clarifying question at a time.
+- If there are multiple viable ways to structure the lab change directory, present 2-3 approaches with trade-offs and a recommendation before freezing the change.
+- Keep an approval gate before locking a change structure that will drive `/lab:run` and `/lab:iterate`.
 
 ## Minimum Task Coverage
 
-- change setup and validation
+- change setup
 - artifact creation
 - validation run
 - evaluation normalization

package/package-assets/shared/skills/lab/stages/write.md

@@ -8,6 +8,21 @@
 - reviewer notes when available
 - vendored paper-writing references under `skills/lab/references/paper-writing/`
 
+## Config Read Set
+
+- `.superlab/config/workflow.json`
+
+## Context Read Set
+
+- `.superlab/context/mission.md`
+- `.superlab/context/decisions.md`
+- `.superlab/context/evidence-index.md`
+
+## Context Write Set
+
+- `.superlab/context/state.md`
+- `.superlab/context/evidence-index.md`
+
 ## Required References
 
 Load the exact vendored file that matches the current target:
@@ -27,6 +42,7 @@ Run these on every round:
 ## Small-Step Writing Rules
 
 - Change one section or one clearly bounded subsection per round.
+- LaTeX is the required manuscript output format.
 - Load only the current section guide. Do not load every section guide at once.
 - Build a compact mini-outline before prose.
 - For each subsection, explicitly include motivation, design, and technical advantage when applicable.
@@ -42,12 +58,20 @@ Run these on every round:
 
 ## Required Artifacts
 
-- `docs/lab/paper/plan.md`
-- `docs/lab/paper/sections/<section>.md`
-- `docs/lab/paper/write-iterations/<n>.md`
+- `.superlab/write/plan.md`
+- `.superlab/write/iterations/<n>.md`
+- `docs/paper/paper.tex`
+- `docs/paper/sections/<section>.tex`
 
 ## Stop Conditions
 
 - the target section is accepted for this round
 - evidence is missing and the workflow must return to `review` or `iterate`
 - the writing loop reaches its declared round limit
+
+## Interaction Contract
+
+- Start with a concise summary of the target section, evidence base, and main writing risk for this round.
+- If a missing assumption would change the section structure or claim strength, ask one clarifying question at a time.
+- If there are multiple defensible narrative structures for the current section, present 2-3 approaches with trade-offs and recommend one before drafting.
+- Keep an approval gate when the chosen narrative structure would materially affect downstream sections or paper-level framing.

package/package-assets/shared/templates/design.md

@@ -1,9 +1,9 @@
 # Design
 
-## OpenSpec Change
+## Lab Change
 
 - Change id:
-- Capability or spec area:
+- Target path: `.superlab/changes/<change-id>/design.md`
 
 ## Research Approach
 
@@ -27,7 +27,7 @@ Describe the method and why it is plausible.
 - Normalized summary path:
 - Iteration report path:
 
-## OpenSpec Status
+## Change Links
 
-- `openspec-cn status --change <change-id>`:
-- `openspec-cn validate <change-id>`:
+- Spec path: `.superlab/changes/<change-id>/spec.md`
+- Tasks path: `.superlab/changes/<change-id>/tasks.md`

package/package-assets/shared/templates/paper-section.tex

@@ -0,0 +1,10 @@
+% Section file generated by /lab:write
+% Final manuscript language should be chosen for the paper itself.
+
+\section{Section Title}
+
+% Paragraph 1
+
+% Paragraph 2
+
+% Paragraph 3

package/package-assets/shared/templates/paper.tex

@@ -0,0 +1,29 @@
+\documentclass{article}
+\usepackage[utf8]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{hyperref}
+\usepackage{graphicx}
+\usepackage{booktabs}
+
+\title{Paper Title}
+\author{Author Name}
+\date{}
+
+\begin{document}
+\maketitle
+
+\begin{abstract}
+% Keep the final paper language independent from the workflow language.
+\input{sections/abstract}
+\end{abstract}
+
+\input{sections/introduction}
+\input{sections/related_work}
+\input{sections/method}
+\input{sections/experiments}
+\input{sections/conclusion}
+
+\bibliographystyle{plain}
+\bibliography{references}
+
+\end{document}