fkanban-agent

Automate fkanban card implementation through PR creation and merge.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/EdgeVector/last-stack --skill fkanban-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fkanban-agent
Source: https://github.com/EdgeVector/last-stack/tree/main/skills/fkanban-agent
Command: npx skills add https://github.com/EdgeVector/last-stack --skill fkanban-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The fkanban-agent skill ensures a Kanban card is implemented, PR opened, and merged—eliminating stalled or abandoned work by owning the PR to completion.

Core Features & Use Cases

  • Owns a single card through the full merge workflow: implement, open PR, enforce auto-merge, and verify merge.
  • Supports WORK mode (target a specific card) and RECONCILE mode (sweep in-flight cards, resolve or advance).
  • Integrates with LastDB Kanban and CI to drive PRs to a MERGED state; prevents idle-parked or unmerged PRs.

Quick Start

Ask your agent to run the fkanban-agent on a target card slug to start implementing and driving the PR to merge.

Frequently Asked Questions about fkanban-agent

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

FAQPage Schema
How do I automate a Kanban card workflow from implementation to a merged pull request?

To automate a Kanban card workflow to a merged pull request, the fkanban-agent drives end-to-end ownership by implementing the card, opening a PR, enforcing auto-merge, and verifying the final merge.

What is the best way to handle stalled or abandoned Kanban cards with open pull requests?

To handle stalled Kanban cards with open pull requests, use RECONCILE mode to sweep in-flight cards, resolve under-specified blockers, and advance PRs to completion using sleepless watchers.

How do I keep my local development isolated when automating git pull requests?

To keep development isolated when automating git pull requests, the agent implements isolated git worktrees for each card, ensuring separate branches do not interfere with your main workspace during PR creation.

Does LastDB Kanban support automated PR lifecycle management?

LastDB Kanban supports automated PR lifecycle management through the fkanban-agent, which integrates with CI to enforce auto-merge, monitor pull requests, and escalate to review when needed.

How do I resolve under-specified blockers when automating Kanban card merges?

To resolve under-specified blockers when automating Kanban card merges, the agent handles explicit PR lifecycle guidance and transitions unresolved PRs correctly or escalates them to review.