skill intent contract

Engineering Community

Skill notes

Purpose

The intent contract creates a persistent record of user intent that: Captures what the user is trying to accomplish Defines success criteria upfront Establishes boundaries and constraints Travels through the entire workflow

Intent Contract Structure

The intent contract is stored in .claude/session-intent.md and follows this format:

When to Create Intent Contract

Create an intent contract when: User invokes a major workflow (/octo:embrace, /octo:discover, /octo:plan) User explicitly asks to "plan" or "set goals" for a task A workflow requires multiple phases and validation Do NOT create for:

Step 1: Capture Intent

After asking the 3 clarifying questions in a workflow, prompt the user to define: If user selects "Let me describe it", follow up with a text prompt for their custom goal.

Step 2: Write Intent Contract File

Use the Write tool to create .claude/session-intent.md:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Capture Intent

After asking the 3 clarifying questions in a workflow, prompt the user to define: If user selects "Let me describe it", follow up with a text prompt for their custom goal.

02
Step 2: Write Intent Contract File

Use the Write tool to create `.claude/session-intent.md`:

03
Step 3: Reference During Execution

Throughout the workflow, periodically read `.claude/session-intent.md` to: Stay aligned with user goals Make decisions consistent with boundaries Keep stakeholders in mind At key decision points, explicitly say:

04
Step 4: Validate at End

When the workflow completes, read `.claude/session-intent.md` and validate: Validation Process: Read the intent contract Check each success criterion: ✓ Met - explain how

05
Step 5: Update Intent Contract Status

Update the `Status` field in `.claude/session-intent.md`: `active` → workflow in progress `validating` → checking against criteria `completed` → all criteria met, boundaries respected `incomplete` → some criteria not met, gaps identified

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.