fp-init

Generate E2E_TESTS.md specification files from project source code and release history.

6|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/endorhq/flightplanner --skill fp-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fp-init
Source: https://github.com/endorhq/flightplanner/tree/main/skills/fp-init
Command: npx skills add https://github.com/endorhq/flightplanner --skill fp-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of E2E_TESTS.md specification files, providing a structured foundation for end-to-end testing in any project.

Core Features & Use Cases

  • Project Analysis: Analyzes project structure, code, and release history to identify testable features.
  • Spec Generation: Drafts comprehensive E2E_TESTS.md files, including root-level and package-level specifications.
  • Use Case: Kickstart your project's E2E testing strategy by having this Skill automatically generate initial spec files based on your codebase and its evolution.

Quick Start

Use the fp-init skill to bootstrap E2E_TESTS.md specification files for your project.

Frequently Asked Questions about fp-init

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

FAQPage Schema
How do I generate E2E test specifications from an existing codebase?▼

You can generate E2E test specifications by analyzing your project's source code, release history, and architecture. This Skill drafts comprehensive E2E_TESTS.md files, including preconditions, features, and postconditions for practical coverage.

What is the best way to bootstrap end-to-end testing in a monorepo?▼

The best way to bootstrap end-to-end testing in a monorepo is to analyze the project structure to identify testable artifacts, then draft both root-level and package-level E2E_TESTS.md specification files for comprehensive coverage.

Can I create E2E test specs automatically based on my project's release history?▼

Yes, you can automatically create E2E test specs by analyzing your project's release history alongside its source code. The Skill identifies high-impact features and drafts structured E2E_TESTS.md files based on that evolution.

Does this E2E spec generator work with single-package projects or only monorepos?▼

This E2E spec generator works with both single-package projects and monorepos. It analyzes the project structure to identify testable artifacts and drafts comprehensive E2E_TESTS.md specifications regardless of the repository layout.

What should be included in an E2E_TESTS.md specification file?▼

An E2E_TESTS.md specification file should include preconditions, features, and postconditions. This Skill drafts these comprehensive specs by analyzing your codebase and prioritizing user-facing and high-impact features for practical test coverage.