plan-with-docs

Generate structured markdown project plans and task files in a repository.

3|Updated May 7, 2026
One-click install
npx skills add https://github.com/bestdan/workflow-skills --skill plan-with-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-with-docs
Source: https://github.com/bestdan/workflow-skills/tree/main/skills/plan-with-docs
Command: npx skills add https://github.com/bestdan/workflow-skills --skill plan-with-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of losing context and visibility in large, multi-step engineering projects by moving plans out of ephemeral chat sessions and into persistent, version-controlled markdown files.

Core Features & Use Cases

  • Structured Planning: Automatically generates a project overview and individual task files in a dedicated directory.
  • Task Lifecycle Management: Creates PR-sized task files that integrate with existing task loops and promotion workflows.
  • Refinement Loop: Surfaces open questions and architectural trade-offs to ensure plans are vetted before execution.
  • Use Case: When starting a complex feature that spans multiple PRs, use this skill to generate a roadmap of tasks that can be tracked, edited, and committed to the repository.

Quick Start

Run the plan-with-docs skill to create a structured implementation plan for the new authentication module.

Frequently Asked Questions about plan-with-docs

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

FAQPage Schema
How do I persist multi-step engineering plans as structured markdown?

To persist multi-step engineering plans, generate structured markdown files within your repository. This moves project roadmaps out of ephemeral chat sessions into version-controlled task files for continuous tracking.

How do I manage task lifecycle and numbering for complex features spanning multiple PRs?

Manage task lifecycles by creating PR-sized task files in a dedicated directory. The tool handles automatic numbering and cross-linking to integrate seamlessly with existing engineering workflows.

Do I need git integration to generate project scaffolding and task files?

Yes, git integration is required to verify repository state and path exclusions before writing project scaffolding. This ensures your structured markdown plans are safely committed to version control.

What is the best way to surface open questions and architectural trade-offs before execution?

The best way to surface architectural trade-offs is using a refinement loop during markdown plan generation. This vets open questions against architectural documentation standards to ensure plans are robust before execution.

Does this approach enforce architectural documentation standards for task management?

Yes, the approach enforces architectural documentation standards by generating structured project overviews and individual task files. This ensures multi-step engineering workflows maintain rigorous documentation quality.