grace-plan

Generate module contracts, data-flow maps, and knowledge-graph XML artifacts.

3|2|Updated Apr 1, 2026

Search Tags:#planning #architecture #verification #contracts #knowledge-graph #data-flow #grace

Ready to run

npx skills add https://github.com/ShutovKS/tts-server --skill grace-plan-shutovks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grace-plan
Source: https://github.com/ShutovKS/tts-server/tree/main/.opencode/skills/grace-plan
Command: npx skills add https://github.com/ShutovKS/tts-server --skill grace-plan-shutovks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GRACE planning helps teams formalize requirements and technology decisions into a concrete architectural plan, contracts, data flows, and verification references.

Core Features & Use Cases

Contract-first design: define MODULE_CONTRACTs for each module including PURPOSE, SCOPE, DEPENDS, LINKS.
Phase-based planning: structure with Phase 1 through Phase 5 for requirements, architecture, verification surfaces, and rollout plans.
Knowledge graph artifacts: compile docs/knowledge-graph.xml with module nodes and interconnections.
Verification-oriented outputs: produce development-plan.xml and verification-plan.xml to support validation.

Quick Start

Initialize the GRACE planning workflow with grace-init and proceed to Phase 1 requirements analysis.

Frequently Asked Questions about grace-plan

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

FAQPage Schema

How do I plan a modular architecture with defined contracts and data flows?▼

To plan a modular architecture, you define MODULE_CONTRACTs for each module specifying PURPOSE, SCOPE, DEPENDS, and LINKS, then map the data flows between them to enforce contract-first design.

What is contract-first design and when do I need it for architecture planning?▼

Contract-first design is the process of defining strict MODULE_CONTRACTs before implementation, needed when formalizing requirements and technology choices into concrete architectural plans with verifiable module boundaries.

How do I generate verification artifacts for a software architecture plan?▼

You generate verification artifacts by producing development-plan.xml and verification-plan.xml files, which support validation by defining verification surfaces and rollout plans during the architecture planning phases.

Can I use knowledge-graph references to map module interconnections in my project?▼

Yes, you can compile a knowledge-graph.xml file containing module nodes and their interconnections, serving as a structural reference that maps dependencies and relationships across the planned architecture.

Do I need defined requirements and technology choices before starting phase-based architecture planning?▼

Yes, phase-based planning requires defined requirements and technology choices as prerequisites, guiding the progression from Phase 1 requirements analysis through architecture design to verification surfaces and rollout plans.

What is the best way to structure an architecture plan for validation and rollout?▼

The best way to structure an architecture plan for validation is using a phase-based approach that outputs development-plan.xml, verification-plan.xml, and knowledge-graph.xml to support structured validation and rollout.