research-a-bead

Orchestrate research beads into decision drawers and KG triples.

Updated May 3, 2026

Search Tags:#workflow #research #docs #drawer #mempalace #bead-lifecycle #kg

Ready to run

npx skills add https://github.com/fkberthold/loom --skill research-a-bead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research-a-bead
Source: https://github.com/fkberthold/loom/tree/main/skills/research-a-bead
Command: npx skills add https://github.com/fkberthold/loom --skill research-a-bead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, no-code workflow to define, search, synthesize, and file research-oriented beads within the loom lifecycle, ensuring durable decisions and traceable lineage.

Core Features & Use Cases

Phase-driven research bead lifecycle (A1-M5) delivering decision drawers and KG triples.
Integrates with MemPalace, diary, and docs; defers to bead-lifecycle-shell for claim/verify/close/capture.
Triggered by session startup or /working-a-bead router; suitable for architecture exploration, prior-art evaluation, library design decisions.

Quick Start

Invoke the research-a-bead recipe with a clear question to begin the end-to-end research workflow.

Frequently Asked Questions about research-a-bead

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

FAQPage Schema

How do I document architecture decisions with cross-source synthesis and prior-art tracing?▼

To document architecture decisions, this skill orchestrates a research workflow across multiple sources to produce durable decision artifacts, tracing prior art and synthesizing findings into a structured decision drawer within MemPalace.

What is a research bead lifecycle for design-space exploration?▼

A research bead lifecycle is a phase-driven process spanning stages A1 through M5 that guides design-space exploration, ensuring research outputs are filed as decision drawers and knowledge graph triples for traceable lineage.

Can I use this workflow for library evaluation without writing any code?▼

Yes, you can use this structured no-code workflow for library evaluation. It defers all code work to the bead-lifecycle-shell and focuses entirely on defining, searching, synthesizing, and filing research-oriented beads.

How do I start a research bead workflow for a new architecture question?▼

You start by invoking the research workflow with a clear question. It then coordinates the end-to-end lifecycle, applying cross-source synthesis to generate decision documentation and knowledge graph triples.

Does this research workflow integrate with the bead-lifecycle-shell for claim and verification stages?▼

Yes, it integrates directly with the bead-lifecycle-shell. The workflow defers claim, verify, close, and capture operations to the shell while managing research synthesis and output generation through the M1 to M5 stages.

When should I avoid using this skill for research documentation?▼

You should avoid using this skill if your task requires immediate code generation or if you do not need durable decision artifacts, as it is specifically designed for cross-source synthesis and defers code work to the shell.