wtf-p 0.3.0 → 0.5.0

package/vendors/claude/commands/wtfp/new-paper.md

@@ -1,443 +1,169 @@
 ---
 name: wtfp:new-paper
-description: Initialize a new paper with deep context gathering and PROJECT.md
+description: Start a new paper with guided interview and setup
 allowed-tools:
   - Read
   - Bash
   - Write
+  - Glob
+  - Grep
+  - Task
   - AskUserQuestion
 ---
 
-<objective>
-
-Initialize a new academic paper through comprehensive context gathering.
-
-This is the most leveraged moment in any writing project. Deep questioning here means better structure, better arguments, better outcomes.
-
-Creates `.planning/` with PROJECT.md, config.json, and structure documents.
-
-</objective>
-
 <execution_context>
-
 @~/.claude/write-the-f-paper/references/principles.md
 @~/.claude/write-the-f-paper/references/questioning.md
 @~/.claude/write-the-f-paper/templates/project.md
 @~/.claude/write-the-f-paper/templates/config.json
 @~/.claude/write-the-f-paper/venues/
-
 </execution_context>
 
-<process>
-
-<step name="setup">
-
-**MANDATORY FIRST STEP — Execute these checks before ANY user interaction:**
-
-1. **Abort if project exists:**
-   ```bash
-   [ -f .planning/PROJECT.md ] && echo "ERROR: Paper already initialized. Use /wtfp:progress" && exit 1
-   ```
-
-2. **Initialize git repo in THIS directory** (required for version tracking):
-   ```bash
-   if [ -d .git ] || [ -f .git ]; then
-       echo "Git repo exists in current directory"
-   else
-       git init
-       echo "Initialized new git repo"
-   fi
-   ```
-
-3. **Detect existing writing materials (brownfield detection):**
-   ```bash
-   # Check for existing writing files
-   WRITING_FILES=$(find . -name "*.tex" -o -name "*.md" -o -name "*.bib" -o -name "*.docx" 2>/dev/null | grep -v node_modules | grep -v .git | grep -v .planning | head -20)
-   HAS_SOURCES=$([ -d sources ] || [ -d references ] || [ -d literature ] && echo "yes")
-   HAS_SOURCE_MAP=$([ -d .planning/sources ] && echo "yes")
-   ```
-
-   **You MUST run all bash commands above using the Bash tool before proceeding.**
+<objective>
+Initialize a new academic paper through comprehensive context gathering.
 
-</step>
+**Orchestrator role:** Check preconditions, detect brownfield projects, gather paper vision through batched questioning, synthesize PROJECT.md + config.json + structure documents, commit.
 
-<step name="brownfield_offer">
+Creates `.planning/` with PROJECT.md, config.json, and structure documents.
+</objective>
 
-**If existing writing detected and .planning/sources/ doesn't exist:**
+<context>
+No arguments. Runs in current directory.
+</context>
 
-Check the results from setup step:
-- If `WRITING_FILES` is non-empty OR `HAS_SOURCES` is "yes"
-- AND `HAS_SOURCE_MAP` is NOT "yes"
+<process>
 
-Use AskUserQuestion:
-- header: "Existing Material"
-- question: "I detected existing writing materials. Would you like to map them first?"
-- options:
-  - "Map sources first" — Run /wtfp:map-project to index existing literature/drafts (Recommended)
-  - "Skip mapping" — Proceed with paper initialization
+## 1. Validate Environment
 
-**If "Map sources first":**
-```
-Run `/wtfp:map-project` first, then return to `/wtfp:new-paper`
+```bash
+[ -f .planning/PROJECT.md ] && echo "ERROR: Paper already initialized. Use /wtfp:progress" && exit 1
 ```
-Exit command.
-
-**If "Skip mapping":** Continue to type step.
-
-**If no existing materials detected OR sources already mapped:** Continue to type step.
-
-</step>
-
-<step name="type">
-
-**Ask paper type:**
-
-Use AskUserQuestion:
-- header: "Paper Type"
-- question: "What type of document are you writing?"
-- options:
-  - "Research paper" — Journal article or conference paper
-  - "Grant proposal" — Funding application (NSF, NIH, etc.)
-  - "Thesis chapter" — Dissertation or thesis section
-  - "Other" — Essay, report, or something else
-
-Store the document type for later structure decisions.
-
-</step>
-
-<step name="venue_template">
-
-**Select venue template (for research papers):**
-
-If document type is "Research paper", ask for venue template:
-
-Use AskUserQuestion:
-- header: "Venue"
-- question: "What's your target venue or field?"
-- options:
-  - "ACM CS" — Systems, databases, architecture (SIGMOD, OSDI, SOSP)
-  - "IEEE CS" — HPC, parallel systems, storage (SC, IPDPS, TPDS)
-  - "ML/AI" — NeurIPS, ICML, ICLR style
-  - "Nature/Science" — Classic IMRaD for life sciences
-  - "Other" — Custom structure
-
-**Load venue template:**
-
-Based on selection, read the corresponding venue template:
-- ACM CS → `~/.claude/write-the-f-paper/venues/acm-cs.yaml`
-- IEEE CS → `~/.claude/write-the-f-paper/venues/ieee-cs.yaml`
-- ML/AI → `~/.claude/write-the-f-paper/venues/arxiv-ml.yaml`
-- Nature/Science → `~/.claude/write-the-f-paper/venues/nature.yaml`
-- Other → Ask user to describe structure
-
-If document type is "Thesis chapter":
-- Load `~/.claude/write-the-f-paper/venues/thesis-chapter.yaml`
-
-Store the selected venue template for use in structure step.
-
-</step>
-
-<step name="question">
-
-**1. Open (FREEFORM — do NOT use AskUserQuestion):**
-
-Ask inline: "What is the core argument or contribution of your paper?"
-
-Wait for their freeform response. This gives you the context needed to ask intelligent follow-up questions.
-
-**2. Follow the thread (NOW use AskUserQuestion):**
-
-Based on their response, use AskUserQuestion with options that probe what they mentioned:
-- header: "[Topic they mentioned]"
-- question: "You mentioned [X] — how would you describe the key insight?"
-- options: 2-3 interpretations + "Something else"
-
-**3. Target venue:**
-
-Use AskUserQuestion:
-- header: "Venue"
-- question: "What's the target venue or format?"
-- options: Common venues for their field + "Undecided" + "Let me specify"
-
-**4. Sharpen the core:**
 
-Use AskUserQuestion:
-- header: "Core"
-- question: "If reviewers remember one thing, what should it be?"
-- options: Key aspects they've mentioned + "The methodology" + "The findings" + "Something else"
-
-**5. Find boundaries:**
-
-Use AskUserQuestion:
-- header: "Scope"
-- question: "What's explicitly NOT in this paper?"
-- options: Tempting tangents + "Nothing specific" + "Let me list them"
-
-**6. Constraints:**
-
-Use AskUserQuestion:
-- header: "Constraints"
-- question: "Any hard constraints?"
-- options:
-  - "Page/word limit" — Strict length requirements
-  - "Deadline" — Submission deadline pressure
-  - "Data limitations" — Working with specific dataset
-  - "None" — Flexible constraints
-  - "Multiple constraints" — Let me explain
-
-**7. Decision gate:**
-
-Use AskUserQuestion:
-- header: "Ready?"
-- question: "Ready to create PROJECT.md, or explore more?"
-- options (ALL THREE REQUIRED):
-  - "Create PROJECT.md" — Finalize and continue
-  - "Ask more questions" — I'll dig deeper
-  - "Let me add context" — You have more to share
-
-If "Ask more questions" → return to step 2.
-If "Let me add context" → receive input via their response → return to step 2.
-Loop until "Create PROJECT.md" selected.
-
-</step>
-
-<step name="project">
-
-Synthesize all context into `.planning/PROJECT.md`:
-
-```markdown
-# [Paper Title]
-
-## What This Is
-[Paper type, target venue, approximate length]
-
-## Core Argument
-[The thesis in 1-2 sentences — the one thing reviewers should remember]
-
-## Requirements
-
-### Must Have
-- [ ] [Required element 1]
-- [ ] [Required element 2]
-- [ ] [Required element 3]
-
-### Should Have
-- [ ] [Desired element 1]
-- [ ] [Desired element 2]
-
-### Out of Scope
-- [Exclusion 1] — [why]
-- [Exclusion 2] — [why]
-
-## Target Audience
-[Who reads this, what they care about, what they already know]
-
-## Constraints
-- [Constraint 1]: [detail]
-- [Constraint 2]: [detail]
-
-## Key Decisions
-
-| Decision | Rationale | Outcome |
-|----------|-----------|---------|
-| [Choice from questioning] | [Why] | — Pending |
-
----
-*Last updated: [date] after initialization*
+Initialize git if needed:
+```bash
+[ -d .git ] || [ -f .git ] || git init
 ```
 
-Do not compress. Capture everything gathered.
-
-</step>
-
-<step name="structure">
+## 2. Brownfield Detection
 
-**Create structure documents:**
-
-Create `.planning/structure/` directory.
-
-**argument-map.md:**
-```markdown
-# Argument Map
-
-## Central Thesis
-[From core argument above]
+```bash
+WRITING_FILES=$(find . -name "*.tex" -o -name "*.md" -o -name "*.bib" -o -name "*.docx" 2>/dev/null | grep -v node_modules | grep -v .git | grep -v .planning | head -20)
+HAS_SOURCES=$([ -d sources ] || [ -d references ] || [ -d literature ] && echo "yes")
+HAS_SOURCE_MAP=$([ -d .planning/sources ] && echo "yes")
+```
 
-## Supporting Claims
-### Claim 1: [Statement]
-- Evidence: [What will support this]
-- Strength: [to be determined]
+**If materials detected and no source map:** Offer `/wtfp:map-project` first via AskUserQuestion.
 
-### Claim 2: [Statement]
-- Evidence: [What will support this]
-- Strength: [to be determined]
+## 3. Gather Core Context (Batched)
 
-## Logical Flow
-[How claims build to thesis]
+Use AskUserQuestion — collect foundations in one turn:
+- header: "Paper Foundations"
+- question: "1. **Type** (Research paper, Grant, Thesis)\n2. **Venue** (NeurIPS, CHI, Nature, etc.)\n3. **Core Argument** (one thing you're proving)\n4. **Audience** (who is this for?)"
+- options: "I provided the details" | "Guide me step-by-step"
 
-## Gaps
-- [Claims needing evidence]
-- [Logical leaps to address]
-```
+If step-by-step selected, ask Type → Venue → Argument sequentially.
 
-**outline.md:**
-```markdown
-# Document Outline
+## 4. Venue Template Selection
 
-## Venue Template: [acm-cs / ieee-cs / arxiv-ml / nature / thesis / custom]
+If ambiguous, ask via AskUserQuestion:
+- header: "Venue Structure"
+- options: "ACM CS" | "IEEE CS" | "ML/AI" | "Nature/Science" | "Thesis"
 
-## Sections
-[Generated from venue template - see ~/.claude/write-the-f-paper/venues/]
+Load corresponding YAML from `~/.claude/write-the-f-paper/venues/`.
 
-| # | Section | Purpose | Word Ratio |
-|---|---------|---------|------------|
-[Populated from venue template structure]
+## 5. Sharpen Core Argument
 
-## Word Budget
-| Section | Target | Current |
-|---------|--------|---------|
-| Abstract | [X] | 0 |
-| [Section 1 from template] | [X] | 0 |
-| [Section 2 from template] | [X] | 0 |
-| [...] | | |
-| Total | [X] | 0 |
+If core_argument was weak, drill down:
+- header: "Refine Core"
+- question: "If reviewers remember ONE thing, what is it?"
+- options: "The Method" | "The Findings" | "The Theory" | "The System"
 
-## Venue Notes
-[From venue template notes field - venue-specific guidance]
-```
+## 6. Gather Constraints
 
-**narrative-arc.md:**
-```markdown
-# Narrative Arc
+- header: "Scope & Limits"
+- question: "1. **Out of Scope?** 2. **Hard Constraints?** (page limits, deadlines)"
+- options: "Provided details" | "No constraints"
 
-## Act 1: The Problem
-- World state: [Current understanding]
-- Tension: [What's missing]
-- Stakes: [Why it matters]
+## 7. Synthesize PROJECT.md
 
-## Act 2: The Journey
-- Approach: [How you tackled it]
-- Discovery: [What you found]
+Write `.planning/PROJECT.md` using template from `~/.claude/write-the-f-paper/templates/project.md`.
 
-## Act 3: The Resolution
-- Insight: [What it means]
-- Transformation: [How understanding changes]
+Populate: What This Is, Core Argument, Requirements (Must/Should/Out of Scope), Target Audience, Constraints, Key Decisions.
 
-## Reader Experience
-- Hook: [Why they keep reading]
-- Payoff: [The "aha" moment]
-```
+## 8. Create Structure Documents
 
-</step>
+Create `.planning/structure/` with:
+- **argument-map.md** — Central thesis, supporting claims, logical flow, gaps
+- **outline.md** — Venue template sections, word budget table
+- **narrative-arc.md** — Problem/Journey/Resolution, reader experience
 
-<step name="mode">
+## 9. Workflow Mode & Config
 
-Ask workflow mode preference:
+Ask mode (Interactive / Flow) and depth (Quick / Standard / Comprehensive) via AskUserQuestion.
 
-Use AskUserQuestion:
+## 9b. Git & Planning Settings
 
-- header: "Mode"
-- question: "How do you want to work?"
+Ask about git tracking via AskUserQuestion:
+- header: "Git & Planning"
+- question: "Track planning documents in git?"
 - options:
-  - "Interactive" — Confirm at each step
-  - "Flow" — Auto-approve, minimize interruptions
+  - "Yes (default)" -- commit_docs: true, planning artifacts are version-controlled
+  - "No" -- commit_docs: false, only paper content is committed
 
-</step>
+Use the answer to set `planning.commit_docs` in config.json.
 
-<step name="depth">
+Ask about branching strategy via AskUserQuestion:
+- header: "Git Branching"
+- question: "Branch strategy for git history?"
+- options:
+  - "None (default)" -- all commits on current branch, git.branching_strategy: "none"
+  - "Section branches" -- one branch per section, merged on review pass, git.branching_strategy: "section"
+  - "Submission branches" -- branch per milestone/submission target, git.branching_strategy: "submission"
 
-Ask planning depth preference:
+Use the answer to set `git.branching_strategy` in config.json.
 
-Use AskUserQuestion:
+## 9c. Write Config
 
-- header: "Depth"
-- question: "How thorough should section planning be?"
-- options:
-  - "Quick" — Draft fast, iterate later (minimal planning)
-  - "Standard" — Balanced planning and writing
-  - "Comprehensive" — Thorough outlines before writing
-
-Create `.planning/config.json`:
-```json
-{
-  "mode": "[chosen mode]",
-  "depth": "[chosen depth]",
-  "document_type": "[paper/grant/thesis/other]",
-  "venue_template": "[acm-cs/ieee-cs/arxiv-ml/nature/thesis/custom]",
-  "citation_style": "[from venue template]",
-  "gates": {
-    "confirm_project": true,
-    "confirm_sections": true,
-    "confirm_outline": true,
-    "confirm_plan": true,
-    "review_before_submit": true
-  }
-}
-```
+Write `.planning/config.json` with the full v0.5.0 schema: mode, depth, document_type, output_format, model_profile ("balanced"), venue_template, gates (8 gate types: confirm_outline, confirm_plan, confirm_write, confirm_review, execute_next_section, issues_review, confirm_transition, confirm_submission), writing, workflow, verification, planning (commit_docs, search_gitignored), parallelization, safety (always_confirm_destructive, always_confirm_external_services, backup_before_major_edits), git (branching_strategy, section_branch_template, submission_branch_template, squash_on_merge).
 
-</step>
-
-<step name="commit">
+## 10. Commit
 
 ```bash
 git add .planning/PROJECT.md .planning/config.json .planning/structure/
-git commit -m "$(cat <<'EOF'
-docs: initialize [paper-title]
-
-[One-liner core argument]
-
-Creates PROJECT.md with paper vision and structure documents.
-EOF
-)"
+git commit -m "docs: initialize [paper-title]"
 ```
 
-</step>
-
-<step name="done">
+</process>
 
-Present completion with next steps:
+<offer_next>
 
-```
-Paper initialized:
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ WTF-P ► PAPER INITIALIZED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 - Project: .planning/PROJECT.md
-- Config: .planning/config.json (mode: [chosen mode])
-- Structure: .planning/structure/ (argument-map, outline, narrative-arc)
-[If .planning/sources/ exists:] - Sources: .planning/sources/ (literature, data, prior-drafts)
+- Config: .planning/config.json (mode: [chosen])
+- Structure: .planning/structure/
 
----
+───────────────────────────────────────────
 
 ## ▶ Next Up
 
-**[Paper Title]** — create section outline
+**Create section outline**
 
 `/wtfp:create-outline`
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-```
+───────────────────────────────────────────
 
-</step>
-
-</process>
-
-<output>
-
-- `.planning/PROJECT.md`
-- `.planning/config.json`
-- `.planning/structure/argument-map.md`
-- `.planning/structure/outline.md`
-- `.planning/structure/narrative-arc.md`
-
-</output>
+</offer_next>
 
 <success_criteria>
-
 - [ ] Deep questioning completed (not rushed)
 - [ ] PROJECT.md captures paper vision with core argument
 - [ ] Structure documents created (argument-map, outline, narrative-arc)
-- [ ] config.json has workflow mode
+- [ ] config.json has gates, safety, planning, and git sections
+- [ ] config.json has workflow mode and model_profile
 - [ ] All committed to git
-
 </success_criteria>

package/vendors/claude/commands/wtfp/pause-writing.md

@@ -1,6 +1,6 @@
 ---
 name: wtfp:pause-writing
-description: Create context handoff when pausing work mid-section
+description: Save current progress so you can resume later
 allowed-tools:
   - Read
   - Bash