--- name: gsd:list-phase-assumptions description: Surface Claude's assumptions about…

Community ralph loop for docs, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
--- name: gsd:list-phase-assumptions description: Surface Claude's assumptions about a phase approach before planning argument-hint: '[phase]' allowed-tools: - Read - Bash - Grep - Glob --- <objective> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies. Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective> <execution context> @/Users/gletallec/Documents/NEOPRO/neopro/.claude/get-shit-done/workflows/list-phase-assumptions.md </execution context> <context> Phase number: $ARGUMENTS (required) Project state and roadmap are loaded in-workflow using targeted reads. </context> <process> 1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow list-phase-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt
claude-code

Source: Tallec7

More docs loops

Keep docs in sync with main

/schedulenew

On every push to main, check whether changed code drifted from the docs in /docs and open a PR fixing anything out of date.

prompt
→ Claude
/schedule on every push to main, check whether the changed code drifted from the docs in /docs, and open a PR fixing anything out of date
docshigh risk

--- allowed-tools: Read, Write, Bash, Glob, WebFetch argument-hint…

/ralphnew

Community ralph loop for docs, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
--- allowed-tools: Read, Write, Bash, Glob, WebFetch argument-hint: <input> [lang] description: Generate copy-pastable X/Twitter threads from blog posts, articles, PDFs, or URLs with 3 format options --- # X/Twitter Thread Generator Generate a copy-pastable X thread from any content source - blog posts, articles, PDFs, URLs, or plain text. Usage: $ARGUMENTS Process: 1. Parse Input Arguments - Extract content input and optional language parameter - Examples: - 2025-10-06-my-post (slug only, default English) - 2025-10-06-my-post ja (slug with Japanese) - path/to/article.md (file path) - https://myblog.com/post (URL) - docs/whitepaper.pdf en (PDF with language) 2. Universal Input Detection If input looks like a file path (contains / or file extension): - Use Read tool to check if file exists - Detect format by extension: - .md / .mdx → Parse markdown with frontmatter (extract title, description, body, metadata) - .pdf → Inform user PDF parsing is limited, suggest converting to markdown first - .docx → Inform user DOCX parsing is limited, suggest converting to markdown first -
docsmedium risk

Ralph the docs backlog

Document one undocumented public module per fresh-context iteration, verifying every code sample compiles and accumulating style rules in guardrails so the docs read like one author wrote them.

prompt
→ Claude
/loop fresh context each iteration: read docs-backlog.json, docs/STYLE.md, and .ralph/guardrails.md; pick the top undocumented module, write its reference page with a runnable example, execute the example to prove it works, and mark the module done; add any style or structure decision to .ralph/guardrails.md; stop when the backlog is empty or after 20 turns
docsmedium risk