// Convert feature requirements into structured end-to-end test cases as JSON.
Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.
Quick user-centric interview to capture requirements from a time-poor stakeholder.
Interview me about the plan
Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
Prime yourself on a codebase by listing files and reading the README.
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
| name | plan2json |
| description | Convert feature requirements into structured end-to-end test cases as JSON. |
| argument-hint | <spec-file> |
| disable-model-invocation | true |
| allowed-tools | Read, Write |
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.
Read the file at $1 to get the complete project specification. Read it carefully before proceeding.
Based on the spec file, create feature_list.json with detailed end-to-end test cases.
[
{
"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
}
]
"functional" and "style" categories"passes": falseWrite the JSON array to feature_list.json in the current working directory.