skills.rest
neyrojasj
neyrojasjCOMMUNITY
Explore all skills by this author →
GitHub

planning

Generate markdown-based plans and ADRs for software initiatives.

Updated Nov 26, 2025
Search Tags:#planning#architecture#documentation#adr#milestones#phases
One-click install
npx skills add https://github.com/neyrojasj/smart-agent --skill planning-neyrojasj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/neyrojasj/smart-agent/tree/main/.github/skills/planning
Command: npx skills add https://github.com/neyrojasj/smart-agent --skill planning-neyrojasj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and documenting complex software initiatives with repeatable, markdown-based plans and ADRs saved to disk.

Core Features & Use Cases

  • Generate PLAN-XXX.md plans with phased milestones and definitions of done.
  • Capture architectural decisions (ADRs), risks, and dependencies to guide implementation.
  • Persist plans and knowledge artifacts to .github/copilot/plans/ for auditability and reuse.

Quick Start

Create PLAN-XXX.md with a phased execution plan for integrating a new feature into the project.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a phased execution plan with milestones for a complex software project?▼

Architecture decision records document architectural choices, risks, and dependencies to guide implementation. They are generated as markdown-based ADR files and persisted alongside plans to disk, ensuring auditability and knowledge reuse throughout the software lifecycle.

Can I use this planning approach for both small enhancements and large project rewrites?▼

Plan and knowledge artifacts are persisted as markdown files to the `.github/copilot/plans/` directory on disk. Saving plans and ADRs to this specific location ensures auditability, historical tracking, and reuse across the project lifecycle.

What is the best way to document non-functional requirements alongside software milestones?▼

Mandatory clarifying questions are enforced before plan generation to ensure all project context, non-functional requirements, and architectural risks are fully understood. This prevents incomplete planning by forcing explicit definition of scope and Definition of Done before execution begins.

Does this planning process generate a knowledge file to guide software implementation?▼

Yes, the planning process produces a knowledge file designed to guide implementation alongside the markdown-based plan. This knowledge artifact captures architectural decisions and context, providing a persistent reference for developers throughout the execution phases.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
CleanExpoCleanExpo
1

outcome-translator

Convert founder outcome statements into engineering execution plans with definitions of done.

Community
Advanced
outfitter-devoutfitter-dev
6

check-status

Aggregate project status from VCS, code review, issue trackers, and CI/CD pipelines.

Official
Advanced
SensLiaoSensLiao

gsd-ns-project

Create, complete, audit, and summarize project milestones.

Community
Basic