/**
 * Mapping from ContextCapabilityFlags → library process paths.
 *
 * When a capability flag is true, the babysit skill should prefer dispatching
 * the listed process(es) for work in that context. This is the consumer side
 * of the capability-emission added in `instructions.ts` — it closes the loop
 * between "detect context → emit flags" and "use flags → select a process".
 *
 * Paths are relative to the active process-library root. Multiple processes
 * may be listed per flag in priority order (first match wins unless the
 * caller wants to dispatch them all).
 *
 * @module prompts/capabilityProcessMap
 */
import type { ContextCapabilityFlags } from './contextDetect';
export type CapabilityProcessMap = {
    [K in keyof ContextCapabilityFlags]: string[];
};
export declare const CAPABILITY_PROCESS_MAP: CapabilityProcessMap;
/**
 * Return all library process paths whose capability flag is active.
 *
 * Example:
 *   const paths = processPathsForCapabilities(flags);
 *   // → ["specializations/collaboration/github/pr-lifecycle-router.js", ...]
 */
export declare function processPathsForCapabilities(flags: Partial<ContextCapabilityFlags>): string[];
/**
 * Render a markdown block suitable for inclusion in an instructions prompt:
 * lists each active capability and the library process(es) that handle it.
 */
export declare function renderCapabilityProcessGuide(flags: Partial<ContextCapabilityFlags>): string;
//# sourceMappingURL=capabilityProcessMap.d.ts.map