workflows-compound

Automates documenting solved problems into structured files with YAML frontmatter and cross-references.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill workflows-compound-the-rabak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows-compound
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/workflows-compound
Command: npx skills add https://github.com/The-Rabak/naysmith --skill workflows-compound-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates documenting recently solved problems to compound team knowledge. Documents a converged knowledge artifact that can be searched and referenced by the team, reducing repeated effort and speeding up future problem solving.

Core Features & Use Cases

  • Two-phase orchestration with Phase 1 parallel research subagents and Phase 2 assembly into a single markdown file under docs/solutions.
  • Stores structured documentation with YAML frontmatter for easy indexing, linking, and future retrieval.
  • Captures execution context learnings and cross-references related docs and issues to build a connected knowledge graph.
  • Automatically assigns a category and places the final document in docs/solutions/[category]/[filename].md.

Quick Start

Run /workflows-compound with optional context to begin documenting the most recent fix.

Frequently Asked Questions about workflows-compound

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

FAQPage Schema
How do I automate documenting solved problems for a team knowledge base?

Automating documentation of solved problems is handled by generating structured markdown files with YAML frontmatter under docs/solutions. The Skill orchestrates parallel research subagents to capture execution context and cross-references, producing a single categorized markdown file per solution.

What's the best way to structure team documentation with frontmatter for easy retrieval?

Using YAML frontmatter in markdown files enables easy indexing, linking, and retrieval of team documentation. The Skill automatically assigns a category and stores the final document in docs/solutions/[category]/[filename].md, building a connected knowledge graph.

How does parallel subagent orchestration work for generating solution docs?

Parallel subagent orchestration for solution docs runs in two phases: Phase 1 dispatches parallel research subagents to gather execution context, and Phase 2 assembles findings into a single markdown file with YAML frontmatter and cross-references.

Can I capture execution context learnings and cross-reference related issues automatically?

Capturing execution context learnings and cross-referencing related docs and issues is automated during the documentation generation process. This builds a connected knowledge graph within the structured markdown output stored in docs/solutions.

Do I need any specific dependencies to generate structured markdown files for team collaboration?

No external dependencies are required to generate structured markdown files for team collaboration. The Skill operates independently using its internal two-phase orchestration and parallel subagents to produce the final documentation artifacts.

When should I not use automated documentation generation for solved problems?

Automated documentation generation for solved problems is not suited for ad-hoc or incomplete fixes lacking a converged solution. It is designed for finalized problems where structured markdown with frontmatter and cross-references will compound long-term team knowledge.