prescribe

Creates session prescriptions with fields to guide downstream canopy workflow.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/JDHayesBC/Awareness --skill prescribe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prescribe
Source: https://github.com/JDHayesBC/Awareness/tree/main/.claude/skills/prescribe
Command: npx skills add https://github.com/JDHayesBC/Awareness --skill prescribe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session intention-setting helps teams align on the objective, scope, and blockers at the start of a work session.

Core Features & Use Cases

  • Name the work and align on what success looks like
  • Surface blockers and dependencies early to prevent drift
  • Guide downstream work flow into canopy and beyond

Quick Start

State the session's intended work and any blockers before starting canopy.

Frequently Asked Questions about prescribe

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

FAQPage Schema
How do I define session intent to prevent scope creep at the start of work?

Defining session intent requires naming the work, the definition of done, and any blockers before starting. This structured prescription prevents scope creep by surfacing dependencies early and aligning the objective.

What fields are required to create a structured work session prescription?

A structured work session prescription requires specifying What, Done when, Not today, Blockers, Primary files, and Confidence. These fields validate the workflow for a deterministic handoff to downstream steps.

How does surfacing blockers early improve downstream workflow coordination?

Surfacing blockers early improves coordination by preventing drift and scope creep. The prescription validates these dependencies at the start, enabling a deterministic handoff to coordinate downstream work flows.

Can I use session intention-setting to align on what success looks like for my team?

Yes, session intention-setting aligns teams on the objective by naming the work and the definition of done. This ensures everyone understands what success looks like before downstream execution begins.

What is the best way to document definition of done and primary files before starting a task?

The best way to document definition of done and primary files is through a structured prescription. It validates these fields early to prevent scope creep and ensures deterministic handoff.

When should I not use a structured prescription for my work session?

You should not use a structured prescription for work sessions where scope is entirely undefined or exploratory. It requires knowing the definition of done and primary files to validate a deterministic handoff.