close-out

Automate PR creation, brain checkpointing, and Kanban follow-ups for completed changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Substantive work often ends without a formal close-out: no PR, no brain checkpoint, and no follow-up Kanban card. This Skill automates the end-to-end close-out loop to ensure changes are properly merged, decisions are captured, and next steps are tracked.

Core Features & Use Cases

  • PR creation and auto-merge orchestration: move changes from a worktree into a formal PR and drive it through the repository's merge policy.
  • Brain checkpointing: record the rationale, decisions, and milestones to LastDB brain for long-term context.
  • Kanban follow-up: file a follow-up card for any resulting work item to keep the board current.
  • Use Case: after delivering a feature or a documentation update, run this loop to close out and propagate context.

Quick Start

Run the close-out loop after finishing a substantive change to automatically create the PR, checkpoint the brain, and file the follow-up Kanban card.

Frequently Asked Questions about close-out

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

FAQPage Schema
How do I automate PR creation and merge after finishing a code change?

To automate PR creation and merge after a code change, use an end-to-end close-out workflow that orchestrates pull request creation via GitHub CLI and drives the change through the repository's merge policy.

What is a close-out workflow in software engineering?

A close-out workflow in software engineering is the process of finalizing substantive code changes by creating a pull request, recording decision rationale in a brain checkpoint, and filing a follow-up Kanban card to track next steps.

How do I checkpoint project decisions and rationale after landing code?

To checkpoint project decisions and rationale after landing code, use a close-out loop that records milestones and context to a brain database, ensuring long-term memory of why specific changes were made.

Does the close-out process work with git worktrees?

Yes, the close-out process works with git worktrees by coordinating directly with them to move changes from the worktree into a formal pull request and drive it through auto-merge.

How do I automatically create a follow-up Kanban card for resulting work items?

To automatically create a follow-up Kanban card for resulting work items, run an automated close-out loop that files a follow-up card on your Kanban surface, keeping the project board current after changes land.

When should I run an automated close-out loop for documentation updates?

You should run an automated close-out loop for documentation updates after the work has landed, ensuring the changes are properly merged, decisions are captured in the brain, and next steps are tracked on Kanban.