methodology-extract

Translate problems and materials into actionable methodology via collision-based extraction.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fagemx/prismstack --skill methodology-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: methodology-extract
Source: https://github.com/fagemx/prismstack/tree/main/skills/methodology-extract
Command: npx skills add https://github.com/fagemx/prismstack --skill methodology-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill distills user problems and materials into collision-based insights, enabling systematic extraction of actionable principles and their synthesis into a repeatable domain methodology.

Core Features & Use Cases

  • Collision-based extraction: translate A (problem) and B (materials) into useful patterns for problem solving.
  • Collision log: save Collision Notes and reference them when synthesizing methodology.
  • Team consolidation: aggregate multiple sources into a unified methodology with traceable sources.
  • Generate methodology notes: synthesize collisions into a domain-methodology.md with evidence links.

Quick Start

Provide an A problem and a B material to start a collision-based extraction.

Frequently Asked Questions about methodology-extract

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

FAQPage Schema
How do I extract actionable methodology from research materials?

Collision-based extraction cross-references a specific problem against provided materials to identify useful patterns, saving these intersections as collision notes before synthesizing them into a unified methodology.

What is the best way to consolidate team knowledge into a unified methodology?

Consolidate team knowledge by running systematic collisions on multiple source materials, then synthesizing the extracted notes into a single domain-methodology document with traceable references.

How do I generate a methodology document with traceable references?

Generate a methodology document by synthesizing saved collision notes into a domain-methodology.md file, linking evidence and source references to validate each extracted principle.

Can I use WebSearch and Bash to gather materials for domain planning?

Yes, the extraction workflow supports WebSearch to gather external materials and Bash for extraction tasks, feeding the retrieved data into the collision workflow for domain planning.

What do I need to start a collision-based extraction for domain planning?

You need a defined problem statement and corresponding source materials to initiate collision-based extraction, enabling the system to translate them into actionable patterns for domain planning.