analysis-planning
Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.
When & Why to Use This Skill
The Analysis Planning skill provides a structured framework for organizing complex analytical tasks before execution. It helps users break down intricate questions into actionable steps, gather essential context, and establish iterative workflows to ensure high-quality, actionable results. By emphasizing systematic validation and progressive disclosure, it minimizes project risks and enhances the clarity of final recommendations.
Use Cases
- Strategic Problem Solving: Decomposing broad business challenges into a multi-step analytical roadmap to ensure all variables are considered.
- Research Workflow Design: Planning iterative research cycles that include stakeholder feedback loops and quality checkpoints.
- Resource & Timeline Estimation: Defining the necessary context, dependencies, and time requirements for large-scale data analysis projects to improve predictability.
- Standardizing Analysis Requests: Using the structured context-gathering prompts to ensure all team members provide the necessary information before work begins.
| name | analysis-planning |
|---|---|
| description | Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows. |
Analysis Planning
Quick Start
This skill helps you structure analysis approach before starting work.
Context Requirements
Before proceeding, I need:
- Analysis request: Key information needed for this analysis
- Analysis workflow: Key information needed for this analysis
- Time estimates: Key information needed for this analysis
- Dependency patterns: Key information needed for this analysis
Context Gathering
If any required context is missing from our conversation, I'll ask for it using these prompts:
For Analysis request:
"To proceed with analysis planning, I need to understand analysis request.
Please provide:
- [Specific detail 1 about analysis request]
- [Specific detail 2 about analysis request]
- [Optional context that would help]"
For Analysis workflow:
"To proceed with analysis planning, I need to understand analysis workflow.
Please provide:
- [Specific detail 1 about analysis workflow]
- [Specific detail 2 about analysis workflow]
- [Optional context that would help]"
For Time estimates:
"To proceed with analysis planning, I need to understand time estimates.
Please provide:
- [Specific detail 1 about time estimates]
- [Specific detail 2 about time estimates]
- [Optional context that would help]"
Handling Partial Context
If you can only provide some of the context:
- I'll proceed with what's available and note limitations
- I'll use industry standard defaults where appropriate
- I'll ask clarifying questions as needed during the analysis
Workflow
Step 1: Validate Context
Before starting, I'll confirm:
- All required context is available or has reasonable defaults
- The scope and objectives are clear
- Expected outputs align with your needs
Step 2: Execute Core Analysis
Following best practices for analysis planning, I'll:
- Initial assessment - Review provided context and data
- Systematic execution - Follow structured methodology
- Quality checks - Validate intermediate results
- Progressive disclosure - Share findings at logical checkpoints
Step 3: Synthesize Findings
I'll present results in a clear, actionable format:
- Key findings prioritized by importance
- Supporting evidence and visualizations
- Recommendations with implementation guidance
- Limitations and assumptions documented
Step 4: Iterate Based on Feedback
After presenting initial findings:
- Address questions and dive deeper where needed
- Refine analysis based on your feedback
- Provide additional context or alternative approaches
Context Validation
Before executing the full workflow, I verify:
- Context is sufficient for meaningful analysis
- No contradictions in provided information
- Scope is well-defined and achievable
- Expected outputs are clear
Output Template
Analysis Planning Analysis
Generated: [timestamp]
## Context Summary
- [Key context item 1]
- [Key context item 2]
- [Key context item 3]
## Methodology
[Brief description of approach taken]
## Key Findings
1. **Finding 1**: [Observation] - [Implication]
2. **Finding 2**: [Observation] - [Implication]
3. **Finding 3**: [Observation] - [Implication]
## Detailed Analysis
[In-depth analysis with supporting evidence]
## Recommendations
1. **Recommendation 1**: [Action] - [Expected outcome]
2. **Recommendation 2**: [Action] - [Expected outcome]
## Limitations & Assumptions
- [Limitation or assumption 1]
- [Limitation or assumption 2]
## Next Steps
1. [Suggested follow-up action 1]
2. [Suggested follow-up action 2]
Common Context Gaps & Solutions
Scenario: User requests analysis planning without providing context → Response: "I can help with analysis planning! To provide the most relevant analysis, I need [key context items]. Can you share [specific ask]?"
Scenario: Partial context provided → Response: "I have [available context]. I'll proceed with [what's possible] and will note where additional context would improve the analysis."
Scenario: Unclear objectives
→ Response: "To ensure my analysis meets your needs, can you clarify: What decisions will this inform? What format would be most useful?"
Scenario: Domain-specific terminology → Response: "I want to make sure I understand your terminology correctly. When you say [term], do you mean [interpretation]?"
Advanced Options
Once basic analysis is complete, I can offer:
- Deeper investigation - Drill into specific findings
- Alternative approaches - Different analytical lenses
- Sensitivity analysis - Test key assumptions
- Comparative analysis - Benchmark against alternatives
- Visualization options - Different ways to present findings
Just ask if you'd like to explore any of these directions!
Integration with Other Skills
This skill works well in combination with:
- [Related skill 1] - for [complementary analysis]
- [Related skill 2] - for [next step in workflow]
- [Related skill 3] - for [alternative perspective]
Let me know if you'd like to chain multiple analyses together.