skills.rest
shin0720
shin0720COMMUNITY
Explore all skills by this author →
GitHub

auto-plan

Generate EARS-format requirements and implementation plans from codebase analysis.

Updated Apr 24, 2026
Search Tags:#implementation planning#software development#acceptance criteria#spec generation#codebase analysis#requirements drafting
One-click install
npx skills add https://github.com/shin0720/autopus --skill auto-plan-shin0720
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-plan
Source: https://github.com/shin0720/autopus/tree/main/.autopus/plugins/auto/skills/auto-plan
Command: npx skills add https://github.com/shin0720/autopus --skill auto-plan-shin0720

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting project requirements, implementation plans, and acceptance criteria for software development tasks is time-consuming and often inconsistent across teams, leading to misalignment and rework during development cycles.

Core Features & Use Cases

  • Codebase-Aware SPEC Generation: Analyzes existing project code to produce contextually relevant EARS-format requirements, detailed implementation roadmaps, and measurable acceptance criteria.
  • Seamless Workflow Integration: Routes directly to the core Autopus planning workflow, supporting flags for automated execution, multi-model debate, and team collaboration modes.
  • Use Case: When adding a new feature like OAuth2 authentication, this skill automatically creates a full SPEC document aligned with the project's existing code structure, eliminating hours of manual drafting work.

Quick Start

Use the auto-plan skill to generate a complete SPEC document for adding Google and GitHub OAuth2 authentication to the project.

Frequently Asked Questions about auto-plan

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

FAQPage Schema
How do I generate project SPECs from an existing codebase?▼

To generate project SPECs from an existing codebase, you can automate the extraction of structured requirements, implementation plans, and acceptance criteria directly from your source code analysis, eliminating manual drafting work.

What is EARS-format requirement generation for software development?▼

EARS-format requirement generation is a structured method for creating software development specifications that produces context-aware, measurable acceptance criteria and requirement documents to align cross-functional teams.

How do I create an implementation plan for adding a new feature to an existing project?▼

Creating an implementation plan for a new feature involves analyzing your existing project code structure to automatically produce detailed roadmaps, EARS-format requirements, and acceptance criteria tailored to the modifications.

Can I automate acceptance criteria drafting for cross-functional development teams?▼

Yes, you can automate acceptance criteria drafting by routing your codebase analysis through a structured planning workflow, which generates measurable deliverables and context-aware requirements to align cross-functional teams.

Does automated spec generation work without external dependencies?▼

Yes, automated spec generation operates without external dependencies, directly analyzing your project codebase and routing to the core planning workflow to produce implementation roadmaps and requirement documents.

What is the best way to align development teams on task deliverables for system modifications?▼

The best way to align development teams on task deliverables is generating structured SPECs with measurable acceptance criteria and EARS-format requirements from codebase analysis, ensuring consistent context-aware documentation for system modifications.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
dieu-donneedieu-donnee

feature-forge

Identify feature requirements and produce structured EARS specifications, acceptance criteria, and implementation checklists.

Community
Advanced
shin0720shin0720

auto-dev

Trigger the full Autopus plan, go, and sync workflow with a single alias.

Community
Basic
fanguyunfanguyun

feature-forge

Facilitate structured workshops to produce feature specifications, user stories, and acceptance criteria.

Community
Advanced