01 Plan
Generate technical implementation plans, define component behaviors, and extract design details from images.
Install
$ agentstack add skill-ai-driven-dev-framework-01-plan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ai-driven-dev-framework-01-plan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: plan
Produces implementation plans from requirements, state machines for component behavior, and structured component inventories from design images.
Agent delegation
Spawn the planner agent to execute this skill. For tools that do not support context: fork frontmatter: invoke the planner agent explicitly with this skill's content as the prompt.
Available actions
| # | Action | When to use | | --- | ------------------------ | --------------------------------------------------------------------------- | | 01 | plan | Turn requirements into a technical implementation plan saved to a task file | | 02 | components-behavior | Define a frontend component's behavior as a state machine (Mermaid) | | 03 | image-extract-details | Analyze a design image into a hierarchical component inventory |
Routing (run first)
The planner auto-adapts to the INPUT - do not ask the user to choose. Detect the input type and route; do NOT always fall to action 01.
- A design image or mockup is provided ->
03-image-extract-details(then feed the inventory into planning). - The request is about a frontend component's behavior, states, or transitions ->
02-components-behavior. - Anything else (requirements, a feature to build) ->
01-plan.
Actions may chain (e.g. extract from image, then plan). Read and follow each selected action file.
Actions
@actions/01-plan.md@actions/02-components-behavior.md@actions/03-image-extract-details.md
References
@references/plan-status.md- plan lifecyclestatusvalues, meaning, and who writes each. All actions inherit it; do not re-specify the table elsewhere.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ai-driven-dev
- Source: ai-driven-dev/framework
- License: MIT
- Homepage: https://www.ai-driven-dev.fr/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.