analysis-reflection

To conclude an analysis, this Skill loads an analysis design and its Insight Journal, synthesizes accumulated supporting and contradicting events, surfaces open questions, and records a structured reflection to mark the analysis supported, rejected, or inconclusive.

Structured reflection is needed when sufficient evidence exists in an Insight Journal to evaluate hypotheses. It guides you through summarizing events, resolving open questions, and deciding whether to conclude, refine, or branch an analysis design.

The best way to transition an analysis design status is by running a guided three-question workflow that appends reflect, hypothesize, or conclude events to the journal, then suggests the appropriate status transition based on synthesized evidence.

Yes, MCP access is required to review an analysis journal and record reflection events. The Skill must call get_analysis_design, list_analysis_designs, transition_design_status, and append reflect, hypothesize, or conclude events to the journal records.

To create a refined or branched follow-up analysis, the Skill evaluates accumulated journal evidence against original hypotheses, identifies unresolved open questions, and recommends branching actions or a refined follow-up design instead of a direct conclusion.

Yes, you can synthesize open questions and hypothesis decisions from an Insight Journal. The Skill structures loaded journal events to distinguish supporting evidence, list unresolved questions, and recommend status transitions or follow-up workflows.