skills.rest
osovv
osovvCOMMUNITY
Explore all skills by this author →
GitHub

grace-plan

Generate validated development-plan.xml and knowledge-graph.xml from requirements and technology decisions.

233|51|Updated Feb 17, 2026
Search Tags:#planning#architecture#requirements#knowledge-graph#module-contracts#devplan
One-click install
npx skills add https://github.com/osovv/grace-marketplace --skill grace-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grace-plan
Source: https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-plan
Command: npx skills add https://github.com/osovv/grace-marketplace --skill grace-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms written requirements and technology decisions into a validated, contract-first module architecture and a navigable knowledge graph so teams can move from ambiguity to approved implementation plans without generating code prematurely.

Core Features & Use Cases

  • Prerequisite validation: Checks for docs/requirements.xml and docs/technology.xml and prompts to run initialization if they are missing.
  • Contract-first module design: Produces MODULE_CONTRACT entries (purpose, scope, dependencies, links) and classifies modules by type (ENTRY_POINT, CORE_LOGIC, DATA_LAYER, UI_COMPONENT, UTILITY, INTEGRATION).
  • Knowledge graph generation: Emits docs/knowledge-graph.xml with unique M-xxx nodes, function/type annotations, and CrossLinks.
  • Collaborative approval workflow: Presents a structured module breakdown and mental test walkthroughs, waits for user approval, then creates docs/development-plan.xml and knowledge-graph.xml.
  • Use cases: New feature scoping, module refactors, platform integration planning, and design audits before code generation.

Quick Start

Run the grace-plan skill against your project that contains docs/requirements.xml and docs/technology.xml to produce a development-plan.xml and knowledge-graph.xml after approving the proposed architecture.

Frequently Asked Questions about grace-plan

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

FAQPage Schema
How do I generate module architecture and a knowledge graph from project requirements?▼

Module architecture and a knowledge graph are generated by validating requirements and technology decisions, then producing module breakdowns, contracts, and data flows. You need docs/requirements.xml and docs/technology.xml to create development-plan.xml and knowledge-graph.xml.

How does contract-first module design work for a development plan?▼

Contract-first design produces MODULE_CONTRACT entries defining purpose, scope, dependencies, and links, classifying modules by type (ENTRY_POINT, CORE_LOGIC, DATA_LAYER, UI_COMPONENT, UTILITY, INTEGRATION). A structured breakdown is presented for user approval before generating plan artifacts.

What do I need to create a development plan from use cases and stack decisions?▼

You need docs/requirements.xml defining use cases and docs/technology.xml defining stack decisions. If these prerequisite files are missing, the process prompts you to run initialization before proceeding with architectural plan generation.

Can I plan a module refactor without generating code prematurely?▼

Yes, you can plan module refactors by transforming written requirements into validated, contract-first module architecture and a navigable knowledge graph. This moves teams from ambiguity to approved implementation plans without generating code prematurely.

What is included in a knowledge graph generated from architectural requirements?▼

A generated knowledge graph includes unique M-xxx nodes, function and type annotations, and CrossLinks. It is emitted as docs/knowledge-graph.xml alongside docs/development-plan.xml after the proposed architecture passes user approval.

Does architectural plan generation include risk assessments and implementation phases?▼

Yes, architectural plan generation includes risk assessments and implementation phases within the output development-plan.xml. The process enforces collaborative approval of the module breakdown and mental test walkthroughs before creating these artifacts.

Related Skills

Explore More Software Engineering Skills→
ShutovKSShutovKS
3

grace-init

Create GRACE project scaffolding with docs/, AGENTS.md, and XML templates.

Community
Intermediate
ShutovKSShutovKS
3

grace-plan

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

Community
Advanced
lidessenlidessen
3

engineering

Guide technical decisions with structured reasoning templates and validation criteria.

Community
Advanced
GuidoBergmanGuidoBergman

create-excalidraw-diagram

Generate system architecture, ERD, and UML diagrams in Excalidraw format.

Community
Intermediate