Skip to content

feat: add technical-research skill as preliminary workflow phase#16

Merged
leeovery merged 6 commits intomainfrom
claude/add-technical-research-skill-gt8ge
Dec 17, 2025
Merged

feat: add technical-research skill as preliminary workflow phase#16
leeovery merged 6 commits intomainfrom
claude/add-technical-research-skill-gt8ge

Conversation

@leeovery
Copy link
Copy Markdown
Owner

Introduce research phase as the first step in the workflow, before
discussion. The research skill helps explore new ideas from their
earliest seed - testing feasibility, market fit, and technical
viability before committing to build.

  • Add technical-research skill with SKILL.md and reference docs
  • Update CLAUDE.md to reflect six-phase workflow
  • Research documents seed the discussion phase

Adds research as Phase 1 of a new six-phase workflow:
1. Research - EXPLORE: ideas, feasibility, market, business, learning
2. Discussion - WHAT and WHY: decisions, architecture, edge cases
3. Specification - REFINE: validate and build standalone spec
4. Planning - HOW: phases, tasks, acceptance criteria
5. Implementation - DOING: tests first, then code
6. Review - VALIDATING: check work against artifacts

New files:
- skills/technical-research/SKILL.md
- skills/technical-research/references/research-guide.md
- commands/start-research.md

Updated:
- All existing skills: five-phase → six-phase workflow sections
- README.md: new diagram, research skill/command tables
- CLAUDE.md: six-phase workflow summary

Research skill features:
- Broad expertise: technical, product, business, market domains
- Free-flowing exploration without constraints
- Prompts before documenting: "Shall I capture that?"
- Critical rules: don't hallucinate, don't expand when documenting

Output structure unchanged: docs/workflow/{topic}/research.md
@leeovery leeovery force-pushed the claude/add-technical-research-skill-gt8ge branch from 811f654 to e89501d Compare December 17, 2025 13:02
Single file per phase is sufficient. Removed references to:
- Multiple files moving to pluralized subdirectories
- research/, discussions/, specifications/, plans/ patterns

Each phase now outputs one file:
- research.md
- discussion.md
- specification.md
- plan.md
- Research: docs/workflow/research/ (flat, semantically named files)
- Discussion: docs/workflow/discussion/{topic}.md
- Specification: docs/workflow/specification/{topic}.md
- Planning: docs/workflow/planning/{topic}.md

Updated all skills, commands, README, and CLAUDE.md with correct paths.
Updated all reference files that still had old topic-first paths:
- README.md (implementation section)
- specification-guide.md
- discussion template.md
- formal-planning.md
- output-linear.md, output-backlog-md.md, output-local-markdown.md
- plan-sources.md, plan-execution.md
- review-checklist.md

All paths now follow phase-first structure:
- docs/workflow/research/ (flat)
- docs/workflow/discussion/{topic}.md
- docs/workflow/specification/{topic}.md
- docs/workflow/planning/{topic}.md
- output-backlog-md.md: removed obsolete backlog/docs/{topic}/ structure
- output-linear.md: updated "same topic directory" reference to explicit path
With phase-first structure, plan files are now {topic}.md in the
planning/ directory, not plan.md. Updated all references:
- plan-sources.md: generic "plan file" instead of "plan.md"
- output-local-markdown.md: Create {topic}.md
- output-backlog-md.md: Read planning/{topic}.md
- SKILL.md and formal-planning.md: Single {topic}.md file
@leeovery leeovery merged commit ca14d37 into main Dec 17, 2025
@leeovery leeovery deleted the claude/add-technical-research-skill-gt8ge branch December 17, 2025 18:03
leeovery added a commit that referenced this pull request Apr 20, 2026
…g-queue fail, pause stdin after rebuild confirm

Three targeted internal cleanups:

- withRetry now lets TypeError / ReferenceError / SyntaxError through
  immediately instead of waiting 7s of backoff. A typo shouldn't burn
  retry budget before the real trace reaches the developer.
  (deferred #9)

- cmdIndexBulk catch now writes err.stack to stderr after the summary
  line. Debug info is no longer lost just because the user was piping
  stdout. (deferred #10)

- cmdRebuild's readStdinLine now pauses stdin after consuming the
  confirmation line. Irrelevant for the CLI but prevents a library
  consumer from keeping the event loop alive on an idle stream.
  (deferred #16)

Closes deferred-issues #9, #10, #16.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants