ruby
# app/services/user_service.rb:42
def
process_user
(
user
)
# Implementation here
end

AI-Era Considerations: Account for accelerated development with AI pair programming Include prompts or instructions that worked well during research Note which AI tools were used for initial exploration (Claude, Copilot, etc.) Emphasize comprehensive testing given rapid implementation Document any AI-generated code that needs human review 6. Final Review & Submission Origin document cross-check (if plan originated from a requirements doc): Before finalizing, re-read the origin document and verify: Every key decision from the origin document is reflected in the plan The chosen approach matches what was decided in the origin document Constraints and requirements from the origin document are captured in acceptance criteria Open questions from the origin document are either resolved or flagged The origin: frontmatter field points to the correct source file The Sources section includes the origin document with a summary of carried-forward decisions Pre-submission Checklist: Title is searchable and descriptive Labels accurately categorize the issue All template sections are complete Links and references are working Acceptance criteria are measurable Add names of files in pseudo code examples and todo lists Add an ERD mermaid diagram if applicable for new model changes Write Plan File REQUIRED: Write the plan file to disk before presenting any options. mkdir -p docs/plans/

Determine daily sequence number

today

$( date +%Y-%m-%d ) last_seq = $( ls docs/plans/$ { today } -*-plan.md 2

/dev/null | grep -oP " ${today} -\K\d{3}" | sort -n | tail -1 ) next_seq = $( printf "%03d" $(( $ { last_seq:-0 } + 1 ) ) ) Use the Write tool to save the complete plan to docs/plans/YYYY-MM-DD-NNN---plan.md (where NNN is $next_seq from the bash command above). This step is mandatory and cannot be skipped — even when running as part of LFG/SLFG or other automated pipelines. Confirm: "Plan written to docs/plans/[filename]" Pipeline mode: If invoked from an automated workflow (LFG, SLFG, or any disable-model-invocation context), skip all AskUserQuestion calls. Make decisions automatically and proceed to writing the plan without interactive prompts. Output Format Filename: Use the date, daily sequence number, and kebab-case filename from Step 2 Title & Categorization. docs/plans/YYYY-MM-DD-NNN---plan.md Examples: ✅ docs/plans/2026-01-15-001-feat-user-authentication-flow-plan.md ✅ docs/plans/2026-02-03-001-fix-checkout-race-condition-plan.md ✅ docs/plans/2026-03-10-002-refactor-api-client-extraction-plan.md ❌ docs/plans/2026-01-15-feat-thing-plan.md (missing sequence number, not descriptive) ❌ docs/plans/2026-01-15-001-feat-new-feature-plan.md (too vague - what feature?) ❌ docs/plans/2026-01-15-001-feat: user auth-plan.md (invalid characters - colon and space) ❌ docs/plans/feat-user-auth-plan.md (missing date prefix and sequence number) Post-Generation Options After writing the plan file, use the AskUserQuestion tool to present these options: Question: "Plan ready at docs/plans/YYYY-MM-DD-NNN---plan.md . What would you like to do next?" Options: Open plan in editor - Open the plan file for review Run /deepen-plan - Enhance each section with parallel research agents (best practices, performance, UI) Review and refine - Improve the document through structured self-review Share to Proof - Upload to Proof for collaborative review and sharing Start /ce:work - Begin implementing this plan locally Start /ce:work on remote - Begin implementing in Claude Code on the web (use & to run in background) Create Issue - Create issue in project tracker (GitHub/Linear) Based on selection: Open plan in editor → Run open docs/plans/.md to open the file in the user's default editor /deepen-plan → Call the /deepen-plan command with the plan file path to enhance with research Review and refine → Load document-review skill. Share to Proof → Upload the plan to Proof: CONTENT = $( cat docs/plans/ < plan_filename

.md ) TITLE = "Plan: " RESPONSE = $( curl -s -X POST https://www.proofeditor.ai/share/markdown \ -H "Content-Type: application/json" \ -d " $( jq -n --arg title " $TITLE " --arg markdown " $CONTENT " --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}' ) " ) PROOF_URL = $( echo " $RESPONSE " | jq -r '.tokenUrl' ) Display: View & collaborate in Proof: — skip silently if curl fails. Then return to options. /ce:work → Call the /ce:work command with the plan file path /ce:work on remote → Run /ce:work docs/plans/.md & to start work in background for Claude Code web Create Issue → See "Issue Creation" section below Other (automatically provided) → Accept free text for rework or specific changes Note: If running /ce:plan with ultrathink enabled, automatically run /deepen-plan after plan creation for maximum depth and grounding. Loop back to options after Simplify or Other changes until user selects /ce:work or another action. Issue Creation When user selects "Create Issue", detect their project tracker from AGENTS.md: Check for tracker preference in the user's AGENTS.md (global or project). If AGENTS.md is absent, fall back to CLAUDE.md: Look for project_tracker: github or project_tracker: linear Or look for mentions of "GitHub Issues" or "Linear" in their workflow section If GitHub: Use the title and type from Step 2 (already in context - no need to re-read the file): gh issue create --title ":