skills.rest
ryan-mahoney
ryan-mahoneyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specops-initial-plan

Extract implementation-language-agnostic specifications from codebases and related artifacts.

Updated Mar 14, 2026
Search Tags:#architecture#documentation#codebase#specification#inference#specops
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill specops-initial-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specops-initial-plan
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/specops-initial-plan
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill specops-initial-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform a SpecOps analysis to extract a comprehensive, implementation-language-agnostic specification from existing code and related artifacts. This output is intended to be authoritative for future reimplementation, migration, or system redesign.

Core Features & Use Cases

  • SpecOps extraction: Identify and extract a complete, language-agnostic specification spanning code, tests, configs, schemas, and docs.
  • Artifact discovery: Locate relevant artifacts within the TARGET_SCOPE and aggregate evidence with explicit uncertainty where details are missing.
  • Output deliverable: Produce a structured markdown specification that can guide future implementation, migration, or redesign tasks.

Quick Start

Provide the TARGET_SCOPE, or rely on repository context to infer it, to start the SpecOps analysis.

Frequently Asked Questions about specops-initial-plan

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

FAQPage Schema
How do I extract a language-agnostic specification from an existing codebase?▼

You can extract a language-agnostic specification by analyzing source artifacts including code, tests, configs, schemas, and docs to produce structured markdown output for future reimplementation or migration.

What is the best way to document legacy code for a system redesign?▼

The best way to document legacy code for a redesign is performing SpecOps extraction to aggregate evidence across modules and services, explicitly reporting uncertain details where information is missing.

Can I generate migration specifications from source artifacts like configs and schemas?▼

Yes, you can generate migration specifications from source artifacts by locating relevant files within a target scope and aggregating evidence from code, tests, configs, schemas, and documentation.

Does the specification extraction process handle missing or uncertain details in a repository?▼

The specification extraction process handles uncertain details by explicitly reporting them in the output deliverable when evidence is missing from the analyzed codebase, tests, or configuration files.

Do I need to provide a target scope to start the codebase specification analysis?▼

You do not need to explicitly provide a target scope to start codebase specification analysis; you can rely on existing repository context to infer the target scope automatically.

Related Skills

Explore More Software Engineering Skills→
erikhazzarderikhazzard
1

doc__guard-drift

Compare repository documentation against source artifacts to generate drift reports.

Community
Advanced
hotriluanhotriluan
3

planning

Create detailed technical implementation plans with phases, options, and acceptance criteria.

Community
Basic
cryborg1211cryborg1211

Explore Codebase

Map codebase modules, dependencies, and relationships into a knowledge graph.

Community
Intermediate
anderson-0anderson-0
4

architecture-map

Generate Mermaid architecture diagrams from source code with dependency analysis.

Community
Advanced