plan-protocol

To create a structured implementation plan with decision traceability, use a standardized Markdown format with YAML frontmatter, phased progress markers, and hierarchical tasks. Integrate citations using `ref:delegation-id` to link plan decisions directly to their research sources.

Tracking multi-phase project progress in Markdown requires using specific status markers for phases and tasks. Designate active work with a single `← CURRENT` marker alongside YAML frontmatter to maintain clear, auditable progress across hierarchical implementation steps.

Link research sources to project management decisions by integrating citations directly into your implementation plan. Use the `ref:delegation-id` formatting rule within your Markdown structure to ensure every significant decision is connected to its research-based rationale.

Yes, you can use YAML frontmatter for software feature planning and tracking. It enforces consistent formatting for multi-phase implementation plans, providing a structured foundation for project tracking, hierarchical task management, and decision traceability.

No, this planning approach requires no external dependencies. It operates independently using standard Markdown formatting and YAML frontmatter to manage implementation plans, requiring only adherence to specific formatting rules for frontmatter and phase status.

You should not use a standardized Markdown format for implementation plans when your project lacks a research-based rationale or multi-phase development requirements. The structure enforces decision traceability and hierarchical task management, which adds overhead for simple, linear tasks.