prime

Load plan markdown files from plans/<name>/ into conversation context.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill prime-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prime
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/prime
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill prime-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load plan artifacts into conversation context for work that bypasses workflow skills. Workflow skills (design, runbook, orchestrate) have built-in discovery gates. This skill covers the gap: fixing a blocker, revising an outline, patching a runbook-outline, debugging plan infrastructure.

Core Features & Use Cases

  • Load plan artifacts into conversation context for ad-hoc planning outside workflow skills.
  • Read plan files in specific order: requirements.md, outline.md, design.md, runbook-outline.md, plus any other .md files found in plans/<name>/ (excluding recall-artifact.md consumed by /recall).
  • Chain-call /recall to bring plan content into conversation with cumulative tracking.

Quick Start

Provide the path to a plans directory to load its artifacts into context and then recall.

Frequently Asked Questions about prime

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

FAQPage Schema
How do I load plan artifacts into conversation context for ad-hoc planning?

To load plan artifacts for ad-hoc planning, provide the path to a plans directory. The skill reads markdown files like requirements.md, outline.md, design.md, and runbook-outline.md in priority order, then chains to recall to preserve the plan content contextually.

What is the best way to recall plan markdown files outside of standard workflow skills?

Recalling plan markdown files outside standard workflow skills is best handled by reading files from plans/<name>/ in a specific priority order. It bypasses built-in discovery gates to directly load requirements, outlines, and designs into the active context.

Can I use this skill to fix a blocker or patch a runbook outline without running a full workflow?

Yes, you can fix blockers or patch runbook outlines without full workflows. This skill specifically covers the gap of ad-hoc planning, allowing you to load existing plan artifacts and debug plan infrastructure directly within the conversation.

Does the artifact loading process read all markdown files in the plans directory?

The artifact loading process reads markdown files in plans/<name>/ by prioritizing requirements.md, outline.md, design.md, and runbook-outline.md. It also reads any other .md files found, but explicitly excludes recall-artifact.md files consumed by recall.

How does cross-session continuity work when revising plan artifacts?

Cross-session continuity when revising plan artifacts works by chain-calling recall after reading the markdown files. This brings the plan content into the current conversation with cumulative tracking, preserving context across different sessions.