project-to-spec

Generate customer-spec.md and solution-design.md from Itential project workflows, templates, and MOP components.

13|12|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/itential/builder-skills --skill project-to-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-to-spec
Source: https://github.com/itential/builder-skills/tree/main/.claude/skills/project-to-spec
Command: npx skills add https://github.com/itential/builder-skills --skill project-to-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Itential projects often lack complete, maintainable docs. This skill reads an existing project and reverse-engineers its structure into a customer-spec.md (high-level requirements) and solution-design.md (as-built design) to standardize delivery.

Core Features & Use Cases

  • Read workflows, templates, and MOP components from a named project or project ID.
  • Infer business purpose, phases, inputs/outputs, and integration touchpoints to produce two docs for review.
  • Outputs can be handed to /solution-arch-agent for design-only planning or /spec-agent for refinement.

Quick Start

Provide the project name or ID to generate the customer-spec.md and solution-design.md for review.

Frequently Asked Questions about project-to-spec

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

FAQPage Schema
How do I generate documentation for an existing Itential project?

Generate documentation for an existing Itential project by providing the project name or ID, which reads workflows, templates, and MOP components to produce a customer-spec.md and solution-design.md for review.

What is the best way to reverse-engineer workflows into a solution design document?

Reverse-engineer workflows into a solution design document by analyzing existing project structures to infer business purpose, phases, inputs/outputs, and integration touchpoints, outputting an as-built solution-design.md.

Can I extract business requirements from existing workflows and templates?

Extract business requirements from existing workflows and templates by reading project components to infer business intent and design decisions, generating a high-level customer-spec.md document.

Does this documentation process require manual input for each MOP component?

The documentation process does not require manual input for each MOP component, as it automatically pulls workflows, templates, and MOP components by project name or ID to infer the required specifications.

What should I do after generating the customer spec and solution design files?

After generating the customer spec and solution design files, review and correct the outputs, then feed them into the delivery lifecycle by handing them off to the solution-arch-agent or spec-agent.

When should I reverse-engineer a project into specs instead of writing docs from scratch?

Reverse-engineer a project into specs instead of writing docs from scratch when an existing Itential project lacks complete, maintainable documentation and requires standardized delivery outputs for review.