harness-plan-brief

To generate an HTML project plan for non-engineer stakeholders, provide a task description to create a Plan Brief HTML that summarizes understanding, options, risks, acceptance criteria, and confidence. It renders a self-contained HTML artifact suitable for planning previews and handoffs.

A plan brief is a single HTML document that translates a task request into a reviewer-friendly plan before implementation begins. You need it for project planning when non-engineers must understand the intent, approach, risks, and acceptance criteria of an upcoming task.

To surface past decisions and patterns from harness-mem for risk assessment, the Skill searches the current project for relevant archive entries and past patterns. It then incorporates these findings into the plan brief to inform planning and identify risks.

You cannot use the plan brief HTML for actual implementation, code review, or release work. It is intended exclusively for planning previews, approvals, and handoffs before work begins, not for executing development tasks.

Generating a plan brief requires no external dependencies, as the Skill operates independently to search project context and render the HTML artifact. It relies on harness-mem entries within the current project to gather past decisions and patterns.

The best way to summarize upcoming plans for stakeholder approval is to generate a self-contained HTML artifact that conveys understanding, options, risks, and confidence. This plan brief format translates the task request into a clear, reviewer-friendly document.