plan2json
Plan 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.
More from robzolkos/zolkos-agent-skills
catchup
Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
9done
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
8discovery
Quick user-centric interview to capture requirements from a time-poor stakeholder.
8prime
Prime yourself on a codebase by listing files and reading the README.
7interview
Interview me about the plan
7ship
Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.
6