agentleFS
Sign inStart free
sohaibtsohaibt/product-mode/skills/preflight/SKILL.md

preflight

Skill176 starsChanged 34 days agoMITView on GitHub

Fill in the product-mode pre-flight checklist for the current work and save it to .product-mode/checklist/. Use when the user types /preflight.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use adr, ship and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check .product-mode/checklist/ for a checklist on the same topic.

    line 11
  2. Very specific:

    When the user confirms, save the file as .product-mode/checklist/<UTC timestamp>-<work-slug>.md.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pre-flight checklist

Fill in the five pre-flight boxes for the work the user describes. Use the text after the command as the work description. If there is no text, use the current conversation.

  1. Check .product-mode/checklist/ for a checklist on the same topic. If one exists, build on it and tell the user its path.
  2. Draft each box from the conversation, the code, and .product-mode/decisions/:
    • Problem: Whose pain are we solving, in one sentence?
    • Why now: What changed? (evidence, trigger, cost of waiting)
    • Scope: Smallest change that tests the hypothesis
    • Primary metric: The one number we expect to move
    • Reversibility: One-way or two-way door?
  3. Mark each drafted answer validated (the user said it or data shows it) or assumed (you inferred it). Never invent evidence, data, or a baseline.
  4. Show the draft. Ask about empty or assumed boxes in one short batch. Ask only questions whose answers change the work.
  5. When the user confirms, save the file as .product-mode/checklist/<UTC timestamp>-<work-slug>.md. Use the timestamp format 2026-01-31T09-05-00-000Z and a lowercase, hyphenated slug. Use this content:
# Product-Mode Pre-Flight Checklist

**Work:** <work description>
**Date:** <YYYY-MM-DD>

## Answers

- **Problem**: <answer>
- **Why now**: <answer>
- **Scope**: <answer>
- **Primary metric**: <answer>
- **Reversibility**: <answer>

---
*Generated by product-mode /preflight*
  1. Tell the user the saved path. If a box stays empty, write Unknown: <how we will find out> and say that the work proceeds without it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free