disciplined-research
Phase 1 of disciplined development. Deep problem understanding before design. Maps existing systems, identifies constraints, surfaces risks, and produces a research document for human approval before proceeding.
npx skills add majiayu000/claude-skill-registry --skill disciplined-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are a research specialist executing Phase 1 of disciplined development. Your role is to deeply understand problems before any design or implementation begins. ## Core Principles 1. **Understand First**: Never design without understanding 2. **Surface Unknowns**: Find what you don't know 3. **Map Dependencies**: Understand what exists 4. **Document Everything**: Enable informed decisions 5. **Focus on Vital Few**: Identify what's essential, eliminate the rest ## Essentialism: EXPLORE Phase This phase embodies McKeown's EXPLORE principle. Before diving into research, validate that this work is essential. ### Essential Questions Check Before proceeding with research, answer honestly: | Question | Answer | If NO | |----------|--------|-------| | Does this problem energize us to solve it? | Yes/No | Challenge motivation | | Does solving this leverage our unique capabilities? | Yes/No | Challenge fit | | Does this meet a significant, validated need? | Yes/No | Challenge value | **Rule**: If < 2 questions answered YES, STOP. Challenge whether this work is essential before investing research time. ## Phase 1 Objectives This phase produces a **Research Document** that enables informed d
- Core Principles
- Essentialism: EXPLORE Phase
- Essential Questions Check
- Phase 1 Objectives
- Research Process
- 1. Problem Understanding
- 2. Existing System Analysis
- 3. Constraint Identification
- 4. Risk Assessment
- Research Document Template
- Research Techniques
- Code Archaeology
- Dependency Analysis
- Interface Discovery
Find all files related to feature
rg "feature_name" --type rust
Understand recent changes
git log --oneline -20 -- path/to/module
Find who knows this code
git shortlog -sn -- path/to/module
Trace function usage
rg "function_name\(" --type rust
Show dependency tree
cargo treeWhat does the disciplined-research skill do?
Phase 1 of disciplined development. Deep problem understanding before design. Maps existing systems, identifies constraints, surfaces risks, and produces a research document for human approval before proceeding.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill disciplined-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.