Menu
Use when researching technology options before making framework recommendations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enhanced planning system combining UltraPlan's 6-phase pipeline with Clear Thought's 11 structured thinking frameworks. Takes a plain-English idea and produces a complete, AI-executable implementation plan with rigorous thinking at every phase.
Use when defining API endpoints, designing request/response schemas, or establishing API contracts during framework planning.
Use when documenting architectural decisions, comparing technology options, or recording rationale for framework choices.
Use when selecting architecture patterns (MVC, hexagonal, clean, microservices) for a new project.
Use when creating or updating blueprint files in .framework-blueprints/ directory.
Use when designing CI/CD pipelines or creating GitHub Actions / GitLab CI configuration.
| name | research-workflow |
| description | Use when researching technology options before making framework recommendations. |
| allowed-tools | Read, WebSearch, WebFetch |
This skill standardizes how the Framework Developer Orchestrator researches technology options before making recommendations.
**Research Topic:** [e.g., "Database selection for task management app"]
**Key Criteria:**
- [ ] Relational vs document data model
- [ ] Scale requirements
- [ ] Team familiarity
- [ ] Cost constraints
- [ ] Hosting options
For each technology category:
**Options to Research:**
1. [Option A] - [Brief description]
2. [Option B] - [Brief description]
3. [Option C] - [Brief description]
### Research: [Option Name]
**Official Sources:**
- Documentation: [URL]
- Getting Started: [URL]
- Use Cases: [URL]
**Key Facts:**
- Latest stable version: [version]
- License: [license]
- Pricing: [pricing model]
**Claimed Strengths:**
- [Strength 1] (Source: [URL])
- [Strength 2] (Source: [URL])
**Known Limitations:**
- [Limitation 1] (Source: [URL])
- [Limitation 2] (Source: [URL])
**Fit for Our Project:**
- [Analysis of how it fits our needs]
## Comparison Matrix
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| [Criterion 1] | ✅ Excellent | ⚠️ Good | ❌ Poor |
| [Criterion 2] | ⚠️ Good | ✅ Excellent | ⚠️ Good |
| [Criterion 3] | ✅ Excellent | ✅ Excellent | ⚠️ Good |
| **Overall Fit** | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ |
## Recommendation
**Recommended:** [Option]
**Rationale:**
Based on our project requirements:
1. [Reason 1 with source]
2. [Reason 2 with source]
3. [Reason 3 with source]
**Trade-offs Accepted:**
- [What we give up by choosing this]
**Alternative for Consideration:**
If [condition], consider [alternative] instead because [reason].
| Source Type | Example | Trust Level |
|---|---|---|
| Official docs | postgresql.org/docs | Highest |
| Official blog | blog.react.dev | High |
| Official benchmarks | [vendor benchmarks] | High* |
*Note: Vendor benchmarks may be biased
| Source Type | Example | Trust Level |
|---|---|---|
| Established tech blogs | martinfowler.com | High |
| Conference talks | Strange Loop, QCon | High |
| Peer-reviewed comparisons | VLDB, SIGMOD papers | High |
| Source Type | Example | Trust Level |
|---|---|---|
| Medium articles | medium.com/@author | Medium |
| Stack Overflow | stackoverflow.com | Medium |
| Dev.to | dev.to | Medium |
| r/programming | Low-Medium |
## Database Research: [Database Name]
**Category:** Relational | Document | Graph | Time-series | Key-Value
**Official Resources:**
- Documentation: [URL]
- Use Cases: [URL]
**Technical Specs:**
- Query Language: [SQL/NoSQL/Custom]
- ACID Compliance: Full | Document-level | None
- Scaling: Vertical | Horizontal | Both
- Max Connections: [number]
- Storage Engine: [engine]
**Performance (from official benchmarks):**
- Read throughput: [ops/sec]
- Write throughput: [ops/sec]
- Latency: [p99 latency]
**Deployment Options:**
- Self-hosted: [Yes/No]
- Managed: [List providers]
- Serverless: [Yes/No]
**Pricing:**
- Open Source: [Yes/No]
- Managed pricing: [Starting from $X/month]
**Team Familiarity:**
- Ask user: "What's your experience with [database]?"
## Framework Research: [Framework Name]
**Category:** Backend | Frontend | Full-stack
**Official Resources:**
- Documentation: [URL]
- Tutorial: [URL]
- Examples: [URL]
**Technical Specs:**
- Language: [Language]
- Latest Version: [version]
- Release Date: [date]
- License: [license]
**Features:**
- [Feature 1]
- [Feature 2]
- [Feature 3]
**Ecosystem:**
- Package Manager: [npm/pip/etc]
- Number of packages: [count]
- Community size: [GitHub stars, npm downloads]
**Learning Curve:**
- Beginner-friendly: [Yes/No]
- Documentation quality: [Excellent/Good/Fair/Poor]
- Community support: [Active/Moderate/Limited]
site:postgresql.org performance benchmarks
site:react.dev hooks best practices
"PostgreSQL vs MongoDB" site:*.org OR site:*.edu
"React vs Vue 2024" comparison
"we chose PostgreSQL because" site:github.com
"migrated from MongoDB to" case study
## Research Results: [Topic]
I've researched [topic] using official documentation and reliable sources.
### Summary
| Option | Best For | Source |
|--------|----------|--------|
| [A] | [Use case] | [URL] |
| [B] | [Use case] | [URL] |
| [C] | [Use case] | [URL] |
### My Recommendation
Based on your project requirements:
- [Requirement 1]
- [Requirement 2]
I recommend **[Option]** because:
1. [Reason with source]
2. [Reason with source]
### Questions for You
1. [Clarifying question about requirements]
2. [Question about team experience]
What are your thoughts?
If research is more than 6 months old:
Use this workflow in:
Always: