plan-docs

Generate project requirements, specifications, and implementation plans with REQ identifiers.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/narusenia/skills --skill plan-docs-narusenia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-docs
Source: https://github.com/narusenia/skills/tree/main/plan-docs
Command: npx skills add https://github.com/narusenia/skills --skill plan-docs-narusenia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of turning early project ideas into structured requirements, specifications, and implementation plans, while keeping identifiers, scope, and traceability consistent.

Core Features & Use Cases

  • End-to-end planning: Generates requirements, architecture, and implementation tasks from a brief or an existing repository.
  • Traceable documentation: Assigns REQ IDs by scope and maps requirements to tasks for easier review and execution.
  • Iterative workflow: Supports step-by-step review between phases and can update existing docs without overwriting prior work.
  • Use case: Use it when launching a new product feature, documenting an internal tool, or aligning a messy codebase with a clear delivery plan.

Quick Start

Ask the plan-docs skill to create requirements, specifications, and an implementation plan for your project in the docs folder.

Frequently Asked Questions about plan-docs

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

FAQPage Schema
How do I generate project requirements and specifications from a codebase?

To generate project requirements and specifications from a codebase, provide a project description or repository for analysis. The system produces structured architecture docs and task breakdowns under the docs folder, assigning REQ IDs for traceability.

Can I create an implementation plan without overwriting my existing documentation?

You can update existing documentation without overwriting prior work. The iterative workflow supports step-by-step reviews between phases and safely appends new architecture designs and task breakdowns to your current docs.

What is the best way to map requirements to implementation tasks for traceability?

The best way to map requirements to tasks for traceability is using structured REQ-{SCOPE}-{SEQ} identifiers. This assigns unique IDs by scope and directly links generated requirements to their corresponding implementation tasks.

Does the plan generation workflow support feature additions for an existing project?

The plan generation workflow supports feature additions for an existing project. It performs structural or deep repository analysis to align a messy codebase with a clear delivery plan and updated specifications.

How are generated project planning documents organized in the repository?

Generated project planning documents are organized systematically in the repository. The system writes structured requirements, specifications, and implementation plans into distinct docs/requirements, docs/specifications, and docs/implementation folders.