funcspec-writer

Extract business rules from legacy analysis into a technology-agnostic funcspec.md.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill funcspec-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: funcspec-writer
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/funcspec-writer
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill funcspec-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy analysis often yields scattered technical details and implicit rules. This skill consolidates that knowledge into a technology-agnostic functional specification that guides modernization.

Core Features & Use Cases

  • Extracts implicit business rules, data entities, and acceptance criteria from legacy analysis.
  • Generates FRs in Given/When/Then format, with traceability to source components.
  • Produces a complete funcspec.md including actors, data model, integration points, and a clear modernization path.

Quick Start

Run the funcspec-writer on the target modernization slug to generate a complete funcspec.md from the analysis artifacts.

Frequently Asked Questions about funcspec-writer

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

FAQPage Schema
How do I extract business rules from legacy analysis to create a functional specification?

Extract business rules from legacy analysis by identifying implicit logic and data entities, then consolidating them into a technology-agnostic functional specification with formal requirements and traceability to source components.

How do I generate acceptance criteria in Given When Then format for legacy modernization projects?

Generate acceptance criteria in Given/When/Then format by transforming legacy analysis and integration points into formal requirements, producing a complete funcspec.md with traceable Gherkin-style scenarios for stakeholders.

What is a technology-agnostic functional specification and when do I need one for modernization?

A technology-agnostic functional specification consolidates scattered legacy technical details and implicit rules into formal requirements, data entities, and integration maps, needed when guiding modernization projects away from legacy platform constraints.

Can I trace functional requirements back to source components from legacy analysis artifacts?

Yes, you can trace functional requirements back to source components by applying legacy analysis to generate formal FRs with explicit traceability links, ensuring every requirement maps directly to its originating legacy system element.

What should a complete funcspec.md include for legacy system modernization?

A complete funcspec.md should include actors, functional requirements, data model entities, integration point maps, and acceptance criteria with Given/When/Then format, all derived from legacy analysis to guide the modernization path.

Does this functional specification approach work without specific legacy platform dependencies?

Yes, this approach works without specific legacy platform dependencies because it produces a technology-agnostic functional specification, extracting business rules and data models independent of the original implementation technology stack.