flightplan

    1

    Plan, route, and sequence complex development work into checkable, tool-optimized tickets.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    flightplan

    Example session with this skill installed

    /flightplan I need to migrate our auth system from local strategy to Auth0, including the database schema changes and frontend login components.

    • Read your context and instructions
    • Compiled the flightplan
    • Generated the UI component

    I have analyzed the project structure and identified the auth migration requirements. I've created a plan with 8 tickets, routing high-risk database changes to Opus and UI components to Sonnet.

    Flightplan: Auth0 Migration

    The plan is live. You can track progress and copy prompts from the plan page.

    TicketTaskCapabilityModel
    T-01Define Auth0 Tenant Config & Scopesnonehaiku
    T-02Add @auth0/auth0-react dependencynonehaiku
    T-03Migrate User schema to include auth0_idpostgres-mcpopus
    T-04Implement Auth0Provider in App.tsxweb-designsonnet
    T-05Create Login/Logout buttonsweb-designsonnet
    T-06Update API middleware to verify JWTsapi-skillopus
    T-07Refactor Profile component for Auth0 datanonesonnet
    T-08End-to-end auth flow verificationtestingsonnet

    Next steps

    1. Open the plan page: ~/.claude/flightplan/jobs/github.com/acme/app/plan.html
    2. Copy the prompt for T-01 from the page.
    3. Run /model haiku then paste the prompt to begin.

    App.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Development speed suffers when AI agents try to do everything at once, leading to context drift and messy code. This skill prevents that by separating planning from execution, breaking down complex tasks into a sequence of verified, checkable tickets.

    What it does

    • Multi-step planning generates a dependency-ordered sequence of 5 to 15 checkable tickets for complex tasks.
    • Intelligent routing assigns each ticket to the specific skill, subagent, or MCP tool best suited for that specific sub-task.
    • Model optimization selects the appropriate model and effort level based on the task's complexity and risk.
    • Progress tracking maintains a live HTML plan page to log outcomes, evidence, and status for every ticket.
    • Outcome verification judges finished work against strict "Done" criteria before moving to the next ticket.

    How it works

    1. The /flightplan command triggers a deep read of the project context, git logs, and documentation to establish scope and success criteria.
    2. The "Grill" phase tests assumptions with up to four targeted questions to close gaps in the requirements.
    3. The Serve phase generates a precise prompt for the current ticket, which the user pastes to execute the work.
    4. The Record phase validates the result and updates the plan page, either proceeding to the next ticket or flagging a failure.

    Frameworks & tools

    Built for Claude Code. Integrates with the Skill, Agent, AskUserQuestion, and Artifact tools. Manages local state via ~/.claude/flightplan/.

    Why this beats prompting it yourself

    Manual prompting for long tasks often leads to "lazy" code or missed edge cases as the context window fills up. This skill enforces a pause between tickets for user verification and allows for switching models between planning and execution to save costs.

    Use cases

    • Feature kick-offs to break a large PR into smaller, reviewable commits.
    • Bug hunting to sequence investigation, reproduction, and fixing steps.
    • System refactoring to manage risky, multi-file changes without breaking functionality.
    • Resume work to pick up exactly where a previous session left off with full context.

    Known limitations

    Does not perform the actual coding or implementation work itself. Requires a git remote or local path to generate project keys. Plan pages require the Artifact tool for the best experience.

    Does not perform work itself. Requires git remote or path for keys. Best used with Artifacts enabled. Prompts are generated one at a time to prevent stale instructions.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    GitHub
    Node.js

    Permissions

    Terminal / Shell
    Browser
    Network Access

    Allowed Hosts

    github.com
    Listed1 month ago
    Updated28 days ago

    What's inside

    Frequently Asked Questions

    flightplan acts as a high-level architect for your AI agent; it prevents "context drift" and messy code by breaking down large, complex feature requests into a sequence of 5-15 small, verifiable, and tool-optimized tickets.

    This skill is purpose-built for Claude Code and integrates natively with the Skill, Agent, and Artifact tools to manage local state and display live progress pages.

    No, flightplan is an architectural layer that handles planning, routing, and verification; it generates the specific prompts and sequences that you or your coding agent then execute to perform the actual implementation.

    The "Grill" phase is a proactive requirement check where the skill asks up to four targeted questions to resolve ambiguities in your prompt before it begins the sequencing process, ensuring the plan is accurate from the start.

    Yes, the skill maintains a persistent state in your local directory (~/.claude/flightplan/), allowing you to stop a session and resume exactly where you left off with a full audit log of completed tickets.

    Upon purchase, you receive the flightplan skill definition and access to the internal logic for the /flightplan command, along with documentation for integrating it into your existing Claude Code environment.

    New in Workflow Automation