fluxly Search skills… ⌘K 中文 Publish

plan2json

Data Verified
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Data
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
94 / 100 · audit passed
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 special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview plan2json.preview 
---
name: plan2json
description: Convert feature requirements into structured end-to-end test cases as JSON. You are creating the…
category: data
runtime: no special runtime
---

# plan2json output preview

## PART A: Task fit
- Use case: Convert feature requirements into structured end-to-end test cases as 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. runs entirely locally. Works with Claude Code, Cursor, Clin….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Input / Output: featurelist.json / Format” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Convert feature requirements into structured end-to-end test cases as 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. runs entirely locally. Works with Claude Code, Cursor, Clin…”.
- **02** When the source has headings, the agent prioritizes “Input / Output: featurelist.json / Format” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Convert feature requirements into structured end-to-end test cases as JSON. You are creating the foundation for an autonomous de…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “Input”, “Output: featurelist.json”, “Format”, “Requirements”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name plan2json directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “Input / Output: featurelist.json / Format” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

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