skills.rest
rjroy
rjroyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prep-plan

Create persistent implementation plans and save them as lore artifacts.

6|Updated Oct 7, 2025
Search Tags:#planning#documentation#lore#context#artifact
One-click install
npx skills add https://github.com/rjroy/vibe-garden --skill prep-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prep-plan
Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/prep-plan
Command: npx skills add https://github.com/rjroy/vibe-garden --skill prep-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build an implementation plan and save it as a lore artifact.

Core Features & Use Cases

  • Structured plan generation: Draft a concrete, step-by-step plan aligned to a feature goal or spec.
  • Context gathering: Collect insights from the .lore directories (specs, design, research) to ground the plan.
  • Review workflow: Includes a validation step and optional fresh-eyes review to ensure quality.
  • Save and organize: Persist plans to .lore/plans with kebab-case filenames for easy discovery.

Quick Start

Example: prep-plan for a feature like user authentication; draft a plan and save it to .lore/plans/.

Frequently Asked Questions about prep-plan

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

FAQPage Schema
How do I create a structured implementation plan and save it as a persistent artifact?▼

Implementation plans are generated as durable lore artifacts by gathering context from the .lore directory, defining step-by-step actions, running validation, and saving the final plan to .lore/plans with a kebab-case filename.

What is a lore artifact and when do I need one for feature planning?▼

A lore artifact is a persistent, reviewable plan document saved in the .lore directory. You need one when building a feature requires structured context gathering, step definitions, and validation to ensure long-term project alignment.

How do I draft a feature plan that pulls context from existing project specs and research?▼

Drafting a feature plan involves scanning the .lore directories for existing specs, design, and research insights to ground the implementation steps, followed by an optional fresh-eyes review to ensure plan quality before saving.

Does the prep-plan workflow include a validation or review step before finalizing the plan?▼

The plan workflow includes a built-in validation step to check structure and frontmatter standards, plus an optional fresh-eyes review pass to catch issues and ensure the generated implementation plan is fully reviewable.

Can I organize implementation plans using kebab-case filenames for easier discovery?▼

Yes, generated implementation plans are automatically saved to the .lore/plans directory using kebab-case filenames, ensuring the structured artifacts remain organized and easily discoverable for future reference.

Related Skills

Explore More Education & Research Skills→
JamSuiteJamSuite
1

research

Consolidate codebase and external evidence into a structured research.md.

Official
Advanced
rjroyrjroy
6

specify

Generate feature requirement specs with acceptance criteria saved to .lore/specs/[feature-name].md.

Community
Basic
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
HaRu-LLCHaRu-LLC

quality-plan

Define quality objectives, metrics, QA activities, and acceptance criteria for a project.

Community
Intermediate