grimoire-plan

Derive executable task plans from approved grimoire artifacts.

Updated Jan 26, 2025

Search Tags:#automation #planning #artifacts #tasks #bdd #grimoire

Ready to run

npx skills add https://github.com/jlissner/lissner.io --skill grimoire-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grimoire-plan
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-plan
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grimoire planning currently requires manual consolidation of artifacts into executable tasks. This Skill automates deriving implementation tasks from approved grimoire changes, MADR decisions, and feature manifests, ensuring consistency and traceability.

Core Features & Use Cases

Extracts change context from .grimoire/changes, manifest.md, and features to generate a structured task plan.
Produces both step-definition tasks and production-code tasks for each scenario.
Validates alignment with non-goals and ADRs, helping teams stay within scope and maintainability.

Quick Start

Provide the path to an approved change in .grimoire/changes/ and run the planner to generate actionable task lists.

Frequently Asked Questions about grimoire-plan

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

FAQPage Schema

How do I generate executable task plans from approved grimoire artifacts?▼

To generate executable task plans from grimoire artifacts, provide the path to an approved change stored under .grimoire/changes/. The planner automatically extracts manifests and ADRs to produce structured, testable implementation tasks.

What is the best way to automate BDD step-definition and production-code task creation?▼

Automating BDD task creation is done by deriving both step-definition tasks and production-code tasks directly from approved grimoire scenarios and ADRs, ensuring every generated task has precise file paths and assertions for the coding agent.

Can I use grimoire planning to validate implementation tasks against non-goals and ADRs?▼

Yes, grimoire planning validates alignment with non-goals and ADRs during task derivation. This ensures generated implementation tasks stay within scope and maintain consistency with approved architectural decisions.

Does the grimoire planner work with MADR decisions and feature manifests?▼

Yes, the grimoire planner works with MADR decisions and feature manifests. It extracts change context from these artifacts to consolidate approved architectural decisions into actionable, traceable implementation workflows.

Why do I need to manually consolidate grimoire changes into implementation tasks?▼

Manual consolidation of grimoire changes is prone to scope creep and inconsistency. Automating this derivation streamlines implementation work by outputting well-scoped tasks with precise file paths directly from approved docs.

What file paths and inputs are required to derive tasks from grimoire changes?▼

Deriving tasks requires approved changes stored under .grimoire/changes/ along with related manifest.md files. The planner reads these artifacts to generate step-definitions and production-code tasks with specific assertions.