strategy-notebook-expert-cross-weave

Combine two expert strategy threads into an evidence-preserving notebook seam.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rbtkhn/grace-mar --skill strategy-notebook-expert-cross-weave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-notebook-expert-cross-weave
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/strategy-notebook-expert-cross-weave
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill strategy-notebook-expert-cross-weave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning separate expert-thread strategy inputs into a single coherent notebook seam while preserving evidence boundaries and avoiding unsupported merges.

Core Features & Use Cases

  • Expert Thread Weaving: Combines two indexed strategy expert threads into a structured Judgment seam on a strategy notebook calendar page.
  • Evidence-Preserving Composition: Maintains distinct evidence chains, tensions, verification needs, and source pointers during synthesis.
  • Use Case: Use this Skill when a strategy notebook session needs to connect two expert perspectives into one reviewable decision record with Signal, Judgment, Links, and Open sections.

Quick Start

Ask the strategy notebook skill to weave two named expert threads into a cross-weave seam for the relevant calendar day.

Frequently Asked Questions about strategy-notebook-expert-cross-weave

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine expert strategy threads into a single notebook seam?

Weaving expert threads preserves evidence boundaries, source pointers, and verification needs during synthesis. It prevents unsupported merges by keeping each thread's evidence chain distinct within the combined Judgment seam on the strategy notebook calendar page.

Why does my expert strategy synthesis lose source traceability?

Strategy synthesis loses traceability when expert threads merge without evidence boundary preservation. Weaving threads into a structured seam maintains distinct source pointers, tensions, and verification needs to avoid unsupported merges.

What's the best way to track evidence boundaries when merging strategy perspectives?

The best way to track evidence boundaries when merging strategy perspectives is weaving them into a structured seam with Signal, Judgment, Links, and Open sections. This preserves distinct evidence chains and verification needs during composition.

Can I use strategy notebook weaving for batch-analysis tracking and chapter metadata updates?

Yes, strategy notebook weaving applies to workflows involving batch-analysis tracking and chapter metadata updates. It requires structured handling of thread identifiers, evidence boundaries, verification reminders, and strategy documentation paths.

Do I need structured thread identifiers to weave expert perspectives into a decision record?

Yes, you need structured thread identifiers to weave expert perspectives into a reviewable decision record. The strategy notebook workflow requires them to handle evidence boundaries, verification reminders, and strategy documentation paths accurately.