research-first-dev
Research-first development methodology that investigates existing solutions, brainstorms alternatives, and evaluates trade-offs before any implementation begins.
소스 정보
- 저장소
- a5c-ai/babysitter
- 최근 소스 활동
- 2026년 6월 1일 07:46
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,832
- 포크
- 113
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- research-first-dev
- description
- Research-first development methodology that investigates existing solutions, brainstorms alternatives, and evaluates trade-offs before any implementation begins.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
- graph
- {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}
- Parse the request into specific technical requirements
- Identify the domain and relevant technology stack
- List known constraints (time, resources, compatibility)
- Define success criteria
### 2. Existing Solution Search
- Search GitHub for similar implementations
- Check package registries (npm, PyPI, crates.io, etc.)
- Review documentation for framework-specific solutions
- Identify relevant design patterns
- Check for known anti-patterns to avoid
### 3. Alternative Brainstorming
- Generate at least 3 alternative approaches
- Include a "build" option and at least one "buy/reuse" option
- Consider unconventional approaches
### 4. Trade-Off Evaluation
- Complexity: implementation effort, learning curve
- Time: development timeline, time-to-value
- Risk: failure modes, dependency risks, maintenance burden
- Scalability: growth limits, performance under load
- Score each alternative on all 4 axes
### 5. Recommendation
- Rank alternatives by composite score
- Provide clear recommendation with justification
- Include risk mitigation plan for chosen approach
- Define go/no-go criteria
## Iterative Retrieval
- Start broad, narrow based on findings
- Use confidence scoring to decide when to stop
- Maximum 3 retrieval rounds per topic
- Cache findings for reuse in subsequent phases
## When to Use
- New feature development (always)
- Architecture changes
- Technology selection
- Dependency evaluation
- Performance optimization strategy
## Agents Used
- `planner` (primary consumer)
- `architect` (architecture-specific research)
GitHub에서 보기