Dev Plan Generator
Create or update lightweight phased development plan markdown documents for implementation work. Use when the user asks for a 개발 계획 문서, 구현 계획, dev plan, phased implementation plan, implement_*.md, checkbox-based task plan, or asks to formalize scope before coding.
Install
$ agentstack add skill-coreline-ai-codex-devflow-plugin-dev-plan-generator ✓ 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-coreline-ai-codex-devflow-plugin-dev-plan-generator) 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
Dev Plan Generator
Overview
Create a focused implementation plan that fixes scope, prevents uncontrolled expansion, and gives the project a checkbox-based execution history.
Workflow
- Read relevant local docs first:
README.md,AGENTS.md,CLAUDE.md,docs/*.md, and existingdev-plan/*.md. - Clarify the goal, scope, non-goals, constraints, and verification expectations.
- Create a new file under
dev-plan/implement_YYYYMMDD_HHMMSS.mdunless the user explicitly asks to update an existing plan. - Keep the plan implementation-oriented, not a PRD or meeting note.
- Break the work into phases with checkboxes.
- Add self-tests and done criteria for every phase.
- Update checkboxes to match real progress while implementing.
Required Sections
Every plan should include:
개발 목적개발 범위제외 범위참조 문서공통 진행 규칙Phase 상태 요약- one or more
Phasesections
Use references/dev-plan-template.md when a full skeleton is needed.
Rules
- Do not overwrite old plan files.
- Do not add features outside the stated scope.
- Put ambiguous or risky work into a separate phase or follow-up section.
- If parallel implementation is likely, include ownership boundaries and merge order.
- If engineering review is requested, add an
Engineering Reviewsection or call theplan-eng-reviewskill separately.
Script
Use scripts/new_dev_plan.py to scaffold a timestamped plan:
python3 path/to/scripts/new_dev_plan.py --dir dev-plan --title "Short goal"Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: coreline-ai
- Source: coreline-ai/codex-devflow-plugin
- License: MIT
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.