Derive executable task plans from approved grimoire artifacts.
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-plan
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
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.
Provide the path to an approved change in .grimoire/changes/ and run the planner to generate actionable task lists.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
jlissnerGenerate conventional commit messages from staged changes and grimoire context.
ksciusGenerate implementation plans with tasks, file paths, tests, and commits from specs.
nanorepublicaStandardize unit-test coding practices across Claude Code projects.
voidrotGenerate project breakdown plans with Epic, Feature, Story/Enabler, and Test hierarchies.
