context-assembly

Documents conditional context block assembly rules for LLM prompt nodes.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wlee075/chatbot --skill context-assembly-wlee075
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-assembly
Source: https://github.com/wlee075/chatbot/tree/main/skills/context_assembly
Command: npx skills add https://github.com/wlee075/chatbot --skill context-assembly-wlee075

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context-heavy prompt systems across multiple LLM nodes often struggle with maintaining consistent, auditable context blocks. This skill documents the precise rules for which blocks are assembled and injected, preventing duplication, conflicts, and leakage of irrelevant information.

Core Features & Use Cases

  • Conditional block rendering: Only relevant blocks are compiled based on section, iteration, and state.
  • Block templates and helpers: Details the core templates (ELICITOR_CONTEXT_BLOCK, ELICITOR_PRD_BLOCK, etc.) and helpers like _format_prd_so_far used to render the final prompt.
  • Auditable workflow across nodes: Applies to Elicitor, Drafter, and Reflector to maintain consistent behavior and easy change management.

Quick Start

Review the documented assembly rules and apply them to your LLM prompt system to ensure consistent, auditable context injection across nodes.

Frequently Asked Questions about context-assembly

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

FAQPage Schema
How do I manage LLM prompt context blocks across multiple nodes without duplication?

You can conditionally assemble LLM prompt context blocks across multiple nodes by applying documented block-injection rules, which prevent duplication, conflicts, and irrelevant information leakage. Guard rules ensure only relevant context compiles per section and iteration.

What is the best way to maintain consistent context injection across LLM nodes?

The best way to maintain consistent context injection is applying shared block templates and format contracts across Elicitor, Drafter, and Reflector nodes. This auditable workflow ensures reliable behavior and simplifies change management for context-heavy prompt systems.

How does the _format_prd_so_far helper work in prompt context assembly?

The _format_prd_so_far helper renders the accumulated PRD context into the final prompt block. It works alongside core templates like ELICITOR_CONTEXT_BLOCK and ELICITOR_PRD_BLOCK to conditionally inject relevant formatted context into the active LLM node.

When do I need conditional block rendering for my prompt templates?

You need conditional block rendering when your prompt system spans multiple LLM nodes and struggles with maintaining consistent, auditable context. It compiles only relevant blocks based on section, iteration, and state to prevent context conflicts and information leakage.

Can I use these context assembly rules for multi-node LLM workflows beyond drafting?

Yes, the block-injection rules explicitly apply to Elicitor, Drafter, and Reflector nodes to maintain consistent behavior. Any multi-node LLM workflow requiring auditable context blocks and format contracts can adapt these conditional assembly rules.