takeoff

Inventory repository state and recent context to orient agent sessions.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill takeoff-danmestas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: takeoff
Source: https://github.com/danmestas/wardrobe/tree/main/skills/takeoff
Command: npx skills add https://github.com/danmestas/wardrobe --skill takeoff-danmestas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-flight inventory of repository state and recent context to orient the agent at session start, reducing uncertainty and decision fatigue.

Core Features & Use Cases

  • Inventory current branch, status, and worktrees to surface what changed since the last session.
  • Compare against origin/main to surface ahead/behind status and recent commits, plus open PRs and memory entries.
  • Generate a concise situational report and suggested next steps without mutating the repository.

Quick Start

Invoke takeoff at session start to generate a concise inventory and situational report for your current repository.

Frequently Asked Questions about takeoff

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

FAQPage Schema
How do I get a situational snapshot of my git repository at session start?

A git repository situational snapshot inventories current branches, worktrees, PRs, and memory entries to orient the agent. It compares against origin/main to surface ahead/behind status and recent commits without mutating the repository.

What is the best way to orient an AI agent with recent git context before starting work?

Orienting an AI agent with git context requires a pre-flight inventory of repository state, recent commits, and open PRs. This generates a concise situational report with suggested next steps and identifies potential blockers to reduce decision fatigue.

Can I check worktree status and open PRs without modifying my git repository?

Checking worktree status and open PRs uses a read-only inventory process that enforces strict non-mutation behavior. It presents situational findings and possible next actions for user-confirmed execution without altering the repository state.

How do I identify blockers across git branches and worktrees before resuming a session?

Identifying blockers across git branches and worktrees involves applying a repository inventory at session start. This compares current state against origin/main and surfaces ahead/behind status, recent commits, and memory entries to determine where to begin.

Does generating a repository inventory require any dependencies or special setup?

Generating a repository inventory requires no special dependencies or setup. It operates as a standalone session-start tool that reads existing git context, worktrees, and PRs to produce a situational report and suggested next steps.

When should I not use a read-only repository inventory for session orientation?

A read-only repository inventory for session orientation should not be used when you need to immediately mutate branches or resolve worktree conflicts. It presents options for user-confirmed actions but cannot execute changes, making it unsuitable for direct repository modification.