logix-capability-planning-loop

Plan API shapes from Logix capability scenarios into evaluated proposal portfolios.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill logix-capability-planning-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logix-capability-planning-loop
Source: https://github.com/yoyooyooo/logix/tree/main/.codex/skills/logix-capability-planning-loop
Command: npx skills add https://github.com/yoyooyooo/logix --skill logix-capability-planning-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Logix capability planning needs reliable, authority-respecting convergence from scenario/capability inputs into implementation-ready API shape without allowing local success to falsely imply global closure.

Core Features & Use Cases

  • Scenario-to-Portfolio Planning Loop: Selects the next work item, drafts a slice via sub-agents, and synthesizes proposal/collision/principle/proof deltas into the active planning control plane.
  • Adversarial Pressure & Counter-Shape Generation: Challenges frozen shape under capability bundles and produces either adoption, collision/PRIN escalation, or documented no-change burden with status-quo proof.
  • Global Closure Gate & Snapshot Discipline: Runs a mechanical global closure checklist across scenario coverage, projections, collisions, proofs, surface registry status, authority writebacks, and housekeeping; generates scenario-first shape snapshots grounded in the registry.
  • Implementation Probe Lane with Lifecycle Control: Executes minimal executable evidence only when documents cannot decide, tracking probe-local lifecycle and preventing silent promotion into authority or public API.
  • Surface Candidate Registry & Implementation Gap Ledger: Updates a mechanical ledger for public concept candidates and tracks runtime/type/proof implementation status for frozen or authority-linked points.

Quick Start

Tell the agent: continue the planning loop for the current highest-priority Logix capability planning work, updating proposals, collisions, registry, and run-state until the next action and validation status are determined.

Frequently Asked Questions about logix-capability-planning-loop

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

FAQPage Schema
How do I plan API shapes from capability scenarios without falsely claiming global closure?

Multi-agent API shape planning handles capability decomposition by drafting slices via sub-agents, synthesizing proposal and collision deltas, and maintaining a surface candidate registry to ensure implementation readiness across multi-slice workflows.

How do I handle API shape collisions when applying adversarial pressure to capability bundles?

Adversarial pressure challenges frozen API shapes under capability bundles, producing either adoption, collision escalation to PRIN candidates, or documented no-change burden with status-quo proof to resolve shape conflicts.

When should I use an implementation probe lane during capability planning?

Use an implementation probe lane to execute minimal executable evidence only when documents cannot decide an API shape outcome. Track probe-local lifecycle to prevent silent promotion into authority or public API.

What is a surface candidate registry and how does it track implementation gaps?

A surface candidate registry is a mechanical ledger for public concept candidates that tracks runtime, type, and proof implementation status for frozen or authority-linked points to maintain implementation readiness.

Can I use this capability planning loop for multi-slice API decomposition workflows?

Yes, this capability planning loop applies to multi-slice capability decomposition workflow planning, requiring strict use of SSOT sources, Slice Manifest construction, and Decision Policy ordering to drive implementation readiness.