skills.rest
noviadi
noviadiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plan

Generate an implementation plan by analyzing gaps between specs and code.

Updated Jan 27, 2026
Search Tags:#documentation#specs#gap-analysis#implementation-plan#regeneration#plans/IMPLEMENTATION_PLAN.md
One-click install
npx skills add https://github.com/noviadi/agent-loop --skill writing-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plan
Source: https://github.com/noviadi/agent-loop/tree/main/.agents/skills/writing-plan
Command: npx skills add https://github.com/noviadi/agent-loop --skill writing-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the task of translating specifications into concrete, executable implementation plans, reducing manual planning time and ensuring alignment between specs and code.

Core Features & Use Cases

  • Gap analysis between specs and code to identify missing or conflicting requirements.
  • Regeneration of plans/IMPLEMENTATION_PLAN.md to reflect the current project state after spec or code changes.
  • Prerequisites and validation guidance to perform plan generation and verify readiness.

Quick Start

Run the gap-analysis workflow to produce a fresh plans/IMPLEMENTATION_PLAN.md from specs and current source.

Frequently Asked Questions about writing-plan

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

FAQPage Schema
How do I generate an implementation plan from specs and source code?▼

To generate an implementation plan from specs, perform gap analysis between specs in the specs/ directory and the src/ directory, outputting a fresh plans/IMPLEMENTATION_PLAN.md file to guide development.

What is gap analysis between specs and code used for?▼

Gap analysis between specs and code identifies missing or conflicting requirements by comparing specs/ against src/, ensuring your implementation plan accurately reflects the current project state and required work.

How do I regenerate plans/IMPLEMENTATION_PLAN.md after changing specs?▼

To regenerate plans/IMPLEMENTATION_PLAN.md after spec or code changes, run the gap-analysis workflow to compare the updated specs/ directory against the src/ directory and produce a fresh plan.

How do I validate an implementation plan before starting development?▼

Validate an implementation plan by running the ./scripts/verify.sh script, which checks the generated plans/IMPLEMENTATION_PLAN.md for readiness and alignment with the project's specs and source code.

Do I need a verify.sh script to use this implementation plan generation workflow?▼

The implementation plan generation process is validated by running ./scripts/verify.sh, so having this validation script in your project structure ensures the generated plan accurately reflects the gap analysis results.

Why does my implementation plan not match the current codebase state?▼

An implementation plan may not match the codebase because specs or source code changed without regenerating the plan; running the gap-analysis workflow against specs/ and src/ produces a fresh, aligned IMPLEMENTATION_PLAN.md.

Related Skills

Explore More Software Engineering Skills→
softwareByAndisoftwareByAndi

manage-specs

Audit and update specification files in the specs/ directory.

Community
Advanced
llama-farmllama-farm
2

openspec-verify-change

Verify codebase implementations against delta specifications and change artifacts.

Official
Advanced
usuroborusurobor
8

document

Trace documentation claims to code, specs, or upstream documents.

Community
Advanced
tsurutantsurutan

doc-generator

Generate inline and standalone documentation from JavaScript, TypeScript, Python, and Go code.

Community
Intermediate