Enforce required frontmatter, goal context, and decision citations in implementation plans.
npx skills add https://github.com/dmooney/Rundale --skill plan-protocol-dmooney
Please help me install this Agent Skill. Skill: plan-protocol Source: https://github.com/dmooney/Rundale/tree/main/.opencode/skills/plan-protocol Command: npx skills add https://github.com/dmooney/Rundale --skill plan-protocol-dmooney
It prevents incomplete or inconsistent implementation plans by enforcing a required structure, lifecycle rules, and evidence-based citations for decisions.
ref:delegation-id format.← CURRENT task rule.Load the plan-protocol skill and ask an AI to produce a new implementation plan using the exact markdown format specified, including citations in the Context & Decisions table.
High-intent search queries and answers about installing and using this skill.
Implementation plan formatting is standardized by enforcing required YAML frontmatter fields, a defined Goal section, and a Context & Decisions table with evidence-based citations. This prevents incomplete plans by applying structural guardrails and lifecycle rules to every generated document.
Decision citations in an implementation plan must use the specified `ref:delegation-id` format within the Context & Decisions table. This evidence-based citation requirement ensures that every architectural and execution decision is traceable to its originating research or delegation context.
Multi-phase project tracking requires enforcing phase and task status markers with hierarchical task numbering. The schema mandates exactly one in-progress phase and exactly one current task marked with `← CURRENT` to maintain strict progress tracking discipline across the lifecycle.
A structured implementation plan with lifecycle state rules is needed after complex requests or research that informs architecture and execution. It applies to multi-phase implementation tracking where validated structure and evidence-based decision records are required.
Multi-phase implementation tracking requires a Context & Decisions table populated with citations in the `ref:delegation-id` format. You cannot produce a validated plan without evidence-based decision records, as the schema enforces this structure to prevent inconsistent planning.
joshsmithxrmGather context and explore options to inform early design decisions.
dianlightExecute one unchecked checklist item from a project task document.
gil0mendesCreate multi-phase implementation plans with YAML frontmatter and citation integration.
mikersaysCreate a project planning directory with YAML frontmatter and markdown files.