plan2json

Data Community

Skill notes

Input

Read the file at $1 to get the complete project specification. Read it carefully before proceeding.

Output: featurelist.json

Based on the spec file, create feature_list.json with detailed end-to-end test cases.

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@majiayu000 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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

```json
[
  {
    "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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.