intent-framing

Frame audience, outcome, format, and constraints into a guiding brief for Cowork sessions.

33|10|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill intent-framing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-framing
Source: https://github.com/andreaswasita/copilot-cowork-dojo/tree/main/skills/intent-framing
Command: npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill intent-framing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frame audience, outcome, format, and constraints into a single guiding brief that every subsequent prompt builds on for a Cowork session.

Core Features & Use Cases

  • Establish a consistent frame at session start to orient all prompts.
  • Enable smooth handoffs between agents and roles through a pinned frame.
  • Use case: when handing a session to another agent or changing direction mid-session, the frame keeps output aligned.

Quick Start

Write a 4-line frame and pin it to the session.

Frequently Asked Questions about intent-framing

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

FAQPage Schema
How do I frame prompts for a Cowork session to maintain alignment?

To frame prompts for a Cowork session, you establish audience, outcome, format, and constraints into a single guiding brief that every subsequent prompt builds on to maintain alignment.

What is the best way to set constraints and audience for prompt engineering?

The best way to set constraints and audience for prompt engineering is to write a four-line frame pinning these parameters to the session start, orienting all subsequent outputs.

How do I hand off a Cowork session to another agent without losing context?

Hand off a Cowork session by pinning a consistent frame that defines the audience, outcome, format, and constraints, enabling smooth transitions between agents and roles.

When do I need to establish a frame for prompt engineering tasks?

You need to establish a frame for prompt engineering tasks when handling non-trivial sessions that require consistent orientation, direction changes, or agent handoffs to keep output aligned.

Does the intent-framing approach require any external dependencies?

The intent-framing approach requires no external dependencies, relying solely on writing a four-line frame to pin audience, outcome, format, and constraints to your session.

Why should I not use prompt framing for simple workflow tasks?

You should not use prompt framing for simple workflow tasks because its scope specifically targets maintaining alignment across prompts and handling direction changes in non-trivial sessions, adding unnecessary overhead otherwise.