context-blackboard

Compile issue, wiki, and codebase context into a compact shared blackboard for workflow stages.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill context-blackboard-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-blackboard
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/context-blackboard
Command: npx skills add https://github.com/vovanostm-public/multica --skill context-blackboard-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-stage agent workflows lose context between stages, forcing downstream agents to re-gather information or work from incomplete knowledge. This Skill consolidates issue data, wiki pages, codebase context, and prior evidence into a compact, durable blackboard that every downstream stage can consume directly. ## Core Features & Use Cases - Context Synthesis: Selects only context relevant to the current workflow variant and summarizes problems, constraints, relevant files, decisions, risks, and open questions. - Source Traceability: Records source references, hashes, and page paths so every claim carries evidence or a confidence level, while keeping raw logs out of the blackboard. - Structured Handoff: Produces typed outputs (context.blackboard, context.sources, context.open_questions) with used_evidence, assumptions, blockers, and confidence fields for cross-stage handoff. - Use Case: In a spec-ops pipeline, after issue classification, run this Skill to build the shared blackboard so planning, implementation, and review stages start without broad re-search. ## Quick Start Compile the issue, wiki, and codebase context for the current stage into a compact blackboard with sources and open questions.

Frequently Asked Questions about context-blackboard

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

FAQPage Schema
How do I share context between stages of an agent workflow?▼

Build a context blackboard that summarizes the problem, constraints, relevant files, decisions, risks, and open questions from issue, wiki, and codebase sources. Downstream stages consume the typed blackboard outputs instead of re-running broad searches.

What inputs does context synthesis for a workflow stage require?▼

It requires the raw issue, wiki context, codebase context, previous stage evidence, and a StageContextPackage. Only context relevant to the current workflow variant is selected and summarized.

What happens when wiki and codebase context conflict?▼

The contradiction is surfaced explicitly rather than silently resolved. Conflicts are recorded on the blackboard so downstream stages and decision gates can handle them with full visibility.

How is oversized context handled in a blackboard?▼

When context exceeds budget, it is summarized and linked to external artifacts instead of embedding raw logs. Every claim must carry a source reference or an explicit confidence level.

What are the limitations of a context blackboard approach?▼

It does not perform unrelated stages, overwrite evidence owned by other stages, or execute privileged actions directly. Unavailable context sources result in a degraded index status rather than fabricated content.