fp-add-spec

Generate E2E_TESTS.md specifications by analyzing package source code and public APIs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of End-to-End (E2E) test specification files (E2E_TESTS.md) by analyzing a package's source code, commands, and public API, reducing the manual effort and ensuring comprehensive test coverage.

Core Features & Use Cases

  • Automated Spec Generation: Analyzes package details to draft structured E2E test specifications.
  • Suite and Feature Identification: Automatically determines test suites and categorizes features (core, edge, error, side-effect, idempotency).
  • Use Case: When developing a new command-line tool, use this Skill to generate an initial E2E_TESTS.md file that outlines how to test its core functionality, error handling, and edge cases based on its CLI arguments and README.

Quick Start

Use the fp-add-spec skill to create a new E2E_TESTS.md specification file for the current package.

Frequently Asked Questions about fp-add-spec

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

FAQPage Schema
How do I generate end-to-end test specifications from source code?

End-to-end test specification generation analyzes package source code, commands, and public APIs to automatically draft a structured E2E_TESTS.md file. This process identifies test suites and categorizes features into core, edge, error, side-effect, and idempotency tests for comprehensive coverage.

What is spec-driven development for AI coding agents?

Spec-driven development for AI coding agents uses automated specification files like E2E_TESTS.md to define testing requirements. By analyzing source code and public APIs, it drafts preconditions and postconditions, providing a structured workflow that guides AI agents in validating core functionality and edge cases.

How do I automate E2E test suite creation for a command-line tool?

Automated E2E test suite creation for a command-line tool analyzes the package details, CLI arguments, and README. It automatically determines relevant test suites and drafts specifications covering error handling, core functionality, and edge cases, reducing manual effort and ensuring comprehensive test coverage.

Can I categorize test features into core, edge, and error cases automatically?

Automatic test feature categorization analyzes source code and public APIs to group features into core, edge, error, side-effect, and idempotency categories. This automated classification structures the E2E_TESTS.md file, ensuring diverse test scenarios are defined without manual sorting.

Does E2E test specification generation work without external dependencies?

E2E test specification generation operates entirely through internal scripts without external dependencies. It analyzes package source code and commands directly to produce the E2E_TESTS.md file, functioning within the existing development environment to support automated spec-driven workflows.

How do I draft preconditions and postconditions for E2E testing?

Drafting preconditions and postconditions for E2E testing is automated by analyzing package source code and public APIs. The generated E2E_TESTS.md file outlines these states alongside categorized features, providing clear setup and teardown requirements for each identified test suite.