excrtx-harness-kanban

Registers pending decisions and resumption points as verified kanban cards with blocked-state governance.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-harness-kanban-elderbernardi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excrtx-harness-kanban
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-harness-kanban
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-harness-kanban-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Session conversations lose pending decisions, architectural choices, and resumption context when they end. This Skill converts executive requests into durable, auditable kanban backlog items with explicit references, pending decisions, and expected outputs so work can resume without reconstructing mental context. ## Core Features & Use Cases - Decision-Blocking Cards: Creates kanban cards that stay in blocked state when awaiting executive decisions, preventing premature execution, and verifies final card state with kanban list and kanban show. - Lightweight TODO Mode: Appends simple pending items to plans/STATUS.md or a root TODO.md when a full kanban card is unnecessary, preserving the executive's strategic wording. - Batch Backlog Intake: Classifies batches of raw items (links, commands, observations) by type, priority (P0-P3), and area, with context, scope, and acceptance criteria per item. - Cross-Session Pending Audit: Audits what remains open across sessions by checking plans, drafts, GitHub issues, and git state, separating living pending items from resolved history. - Use Case: An executive says "remind me to review the TechServ contract next week." The Skill registers a TODO with a deadline, links it to the correct microverso, and confirms the entry persisted. ## Quick Start Ask the agent to register a pending decision or task as a kanban card, for example: "Put the v1 architecture decision on the kanban as blocked until I decide."

Frequently Asked Questions about excrtx-harness-kanban

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

FAQPage Schema
How do I register a pending decision in a kanban backlog?▼

Create a card with a decision-oriented title, mandatory reference file paths, a list of pending decisions, and the expected output on resumption. Set the card state to blocked so it cannot trigger premature execution, then verify with kanban list and kanban show.

When should I use a kanban card versus a lightweight TODO entry?▼

Use a full kanban card when the item involves a blocked decision, formal resumption, or operational tracking. Use lightweight TODO mode (appending to TODO.md or plans/STATUS.md) for simple pending items the executive only wants noted without formal tracking.

Why should pending decisions stay in blocked state instead of ready?▼

A ready state signals the card is executable, which can trigger work before the executive decides. Blocked state communicates that a human decision is required, protecting governance and preventing degraded execution quality.

How do I audit what is still pending across multiple sessions?▼

Search prior sessions for resumption terms like pendente, backlog, and handoff, then check local plans, issue drafts, GitHub issues, and current git status. Classify findings as living pending items, resolved history, triageable drafts, or external blockers.

What are the limitations of kanban-based backlog tracking?▼

Cards created before documenting canonical artifacts become orphaned reminders without context. The system also does not replace GitHub Issues for already-externalized backlogs, and quick session-only reminders do not justify card creation.