plan2json
Scannednpx machina-cli add skill robzolkos/zolkos-agent-skills/plan2json --openclawPlan to JSON
You are creating the foundation for an autonomous development process. Your job is to convert a project specification into a comprehensive feature list that serves as the single source of truth for what needs to be built.
Input
Read the file at $1 to get the complete project specification. Read it carefully before proceeding.
Output: feature_list.json
Based on the spec file, create feature_list.json with detailed end-to-end test cases.
Format
[
{
"category": "functional",
"description": "Brief description of the feature and what this test verifies",
"steps": [
"Step 1: Navigate to relevant page",
"Step 2: Perform action",
"Step 3: Verify expected result"
],
"passes": false
},
{
"category": "style",
"description": "Brief description of UI/UX requirement",
"steps": [
"Step 1: Navigate to page",
"Step 2: Take screenshot",
"Step 3: Verify visual requirements"
],
"passes": false
}
]
Requirements
- Minimum 200 features total with testing steps for each
- Both
"functional"and"style"categories - Mix of narrow tests (2-5 steps) and comprehensive tests (10+ steps)
- At least 25 tests MUST have 10+ steps each
- Order features by priority: fundamental features first
- ALL tests start with
"passes": false - Cover every feature in the spec exhaustively
Write the JSON array to feature_list.json in the current working directory.
Source
git clone https://github.com/robzolkos/zolkos-agent-skills/blob/master/skills/plan2json/SKILL.mdView on GitHub Overview
Plan2json reads a project specification file and outputs feature_list.json containing end-to-end test cases. It creates a single source of truth for what to build by translating requirements into categorized functional and style tests, each with descriptive steps and a false initial passes flag. Features are ordered by priority (fundamental first) to guide testing focus and scope.
How This Skill Works
Technical flow: It reads the spec from the provided path (the first argument), parses the features and requirements, and generates a JSON array where each item has category, description, steps, and passes. All tests start with passes: false by default. The tool enforces a mix of 2-5 step tests and longer 10+ step tests, and orders features by priority.
When to Use It
- When you have a complete project spec and need a runnable feature_list.json that enumerates end-to-end tests.
- When you must include both functional and style tests in a single, exhaustive plan.
- When you want all tests created with an initial passes value of false to enforce review before execution.
- When prioritizing work, to place fundamental features first and progressively cover other areas.
- When exporting a plan for CI/QA to validate feature coverage against the spec.
Quick Start
- Step 1: Provide the spec file path as input (e.g., plan2json <spec-file>).
- Step 2: Run plan2json to generate feature_list.json in the current directory.
- Step 3: Open feature_list.json to review the generated tests and ensure priority order.
Best Practices
- Start from a complete spec; Plan2json mirrors its features into test items.
- Describe each test with a concise description and actionable steps.
- Mix short (2-5 steps) and long (10+ steps) tests to balance coverage.
- Ensure every test starts with passes: false and categories are correctly set.
- Validate that the resulting feature_list.json is valid JSON and aligns with the spec.
Example Use Cases
- A product team converts a feature spec into a detailed web app test plan.
- QA engineers generate an end-to-end test suite with both functional and UI checks for a dashboard.
- An automation engineer feeds a spec into plan2json to seed a test runner.
- A release pipeline imports feature_list.json to verify coverage during CI builds.
- An agency documents test coverage for a mobile app with step-by-step tests.
