write-spec

Co-author formal system specifications in the Pantagruel language through guided conversation.

93|4|Updated Aug 7, 2018
One-click install
npx skills add https://github.com/subsetpark/pantagruel --skill write-spec-subsetpark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/subsetpark/pantagruel/tree/main/.claude/skills/write-spec
Command: npx skills add https://github.com/subsetpark/pantagruel --skill write-spec-subsetpark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill assists users in rigorously designing and writing formal system specifications in the Pantagruel language, ensuring clarity and correctness.

Core Features & Use Cases

  • Guided Specification Writing: Collaboratively define domains, rules, invariants, and actions.
  • Rigorous Thinking: Prompts users to clarify ambiguities and surface implicit assumptions.
  • Progressive Disclosure: Structures specifications logically, from high-level concepts to detailed glosses.
  • Use Case: You need to model a new software system's behavior. Use this Skill to systematically define its entities, states, and operations, resulting in a well-formed Pantagruel specification.

Quick Start

Use the write-spec skill to help me start writing a Pantagruel specification for a library system.

Frequently Asked Questions about write-spec

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

FAQPage Schema
How do I write a formal system specification for complex software behavior?

To write a formal system specification, you can co-author domains, rules, invariants, and actions using the Pantagruel language through a guided conversation that enforces rigorous design and progressive disclosure.

What is Pantagruel and how does it help with system modeling?

Pantagruel is a formal modeling language used to define system specifications, ensuring all specification elements like entities, states, and operations are explicitly defined and validated through rigorous domain design.

How do I start modeling domains and invariants step by step?

Start modeling domains and invariants by initiating a guided co-authoring session that prompts you with clarifying questions to surface implicit assumptions, structuring specifications logically from high-level concepts to detailed glosses.

Can I use formal methods to validate rules without prior specification experience?

Yes, you can validate rules without prior specification experience because the co-authoring process facilitates rigorous thinking by asking clarifying questions and adhering to progressive disclosure principles to systematically define system elements.

What is the best way to define system actions and states explicitly?

The best way to define system actions and states explicitly is through collaborative specification writing that ensures all domains, rules, invariants, and actions are systematically modeled and validated for correctness.

Why do I need to clarify ambiguities when designing formal specifications?

You need to clarify ambiguities when designing formal specifications to surface implicit assumptions, ensuring clarity and correctness by making every specification element explicitly defined and validated within the Pantagruel language.