grimoire-draft

Draft Gherkin feature specifications and MADR architecture decisions collaboratively.

Updated Jan 26, 2025
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grimoire-draft
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-draft
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative drafting of feature specifications (Gherkin) and MADR architecture decisions requires a structured, interactive workflow to capture user needs and translate them into executable artifacts.

Core Features & Use Cases

  • Draft Gherkin feature files from user descriptions and acceptance criteria.
  • Generate MADR decisions documenting trade-offs, choices, and consequences.
  • Route requests to appropriate artifacts and manage iterative refinement with the user.

Quick Start

Initiate a new grimoire-draft session by providing a user story or architectural goal.

Frequently Asked Questions about grimoire-draft

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

FAQPage Schema
How do I draft Gherkin feature specifications from user stories?

Draft Gherkin feature specifications collaboratively by providing a user story or acceptance criteria to initiate an interactive session. The workflow routes your functional descriptions through structured prompts to generate executable behavioral artifacts for product and system design.

What is a MADR architecture decision record and when do I need one?

A MADR architecture decision record documents trade-offs, choices, and consequences for system design. You need one when evaluating architectural goals or new functionality, using structured prompts to collaboratively capture and justify design decisions across product requirements.

Can I generate both feature specs and architecture decisions in the same session?

Yes, you can generate both Gherkin feature specs and MADR architecture decisions in the same session. The workflow routes requests to appropriate artifacts, applying structured prompts to collaboratively capture behavioral artifacts and architectural decisions from your functional descriptions.

What's the best way to document architectural trade-offs for new system requirements?

Document architectural trade-offs by initiating a collaborative session with your architectural goal. The workflow applies structured prompts to route requirements into MADR format, documenting choices and consequences through iterative refinement to satisfy system design artifact generation.

Do I need existing acceptance criteria to generate Gherkin feature files?

You do not need existing acceptance criteria to generate Gherkin feature files. Initiate the session by providing a user story or functional description, and the collaborative workflow applies structured prompts to translate your requirements into executable behavioral artifacts.