Dev Docs

Generate strategic development plans with phased tasks and acceptance criteria.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill dev-docs-joshka0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev Docs
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/dev-docs
Command: npx skills add https://github.com/joshka0/foxctl --skill dev-docs-joshka0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to convert a vague vision into a clear, actionable development plan with phases, tasks, risks, and measurable outcomes.

Core Features & Use Cases

  • Strategic plan generation: Produces a structured plan covering executive summary, current/future state analysis, phased implementation, risk mitigation, and success metrics.
  • Task breakdown with acceptance criteria: Creates prioritized, numbered tasks with explicit dependencies and effort sizing (S/M/L/XL).
  • Operational file outputs: Generates plan, context, and task-tracking documents in a predictable dev/active/[task-name]/ layout to keep work organized.

Quick Start

Ask it to plan your roadmap by describing what you need planned, and it will output the full strategic plan plus the accompanying context and tasks files.

Frequently Asked Questions about Dev Docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague product idea into an actionable strategic plan?

To turn a vague idea into a strategic plan, you need to generate an executive summary, state analysis, and phased implementation with risk mitigation. This process converts unclear execution goals into structured task breakdowns with measurable success metrics.

How do I break down a development roadmap into prioritized tasks with dependencies?

Breaking down a roadmap involves creating prioritized, numbered tasks with explicit dependencies and effort sizing. This task breakdown approach sizes work items as S, M, L, or XL while defining clear acceptance criteria for each implementation phase.

What is the best way to map out risk mitigation and dependencies for engineering planning?

Risk mitigation and dependency mapping for engineering planning are best handled within a comprehensive strategic plan. This plan identifies potential risks across implementation phases and structures task dependencies to ensure clear execution goals and measurable outcomes.

Can I generate a task breakdown that includes acceptance criteria and effort sizing?

Yes, you can generate a task breakdown that includes explicit dependencies, effort sizing categorized as S/M/L/XL, and clear acceptance criteria. This structured breakdown organizes work into prioritized, numbered tasks across distinct implementation phases.

Does strategic planning for product management require predefined context or task-tracking files?

Strategic planning for product management does not require predefined files; it generates them. It automatically outputs plan, context, and task-tracking documents into a predictable directory layout to keep development work organized.