intent

Manage the active intent record for the current git branch.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill intent-sanskarbasnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent
Source: https://github.com/sanskarbasnet/fstack/tree/main/intent
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill intent-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the active intent record for the current git branch, ensuring every branch has exactly one current intent describing its title, body, promises, and what it will not touch.

Core Features & Use Cases

  • Manage the intent record for the current branch, including fields: Title, Body, Promises, Not touching.
  • Use with fstack-brain workflows to share and align work across teammates; supports reading current intent and writing updates to refine scope.

Quick Start

Draft or refine the current branch intent using the command fstack-brain intent write.

Frequently Asked Questions about intent

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

FAQPage Schema
What is a git branch intent and how does it guide safe merges?

A git branch intent is a single active record defining a branch's Title, Body, Promises, and Not touching boundaries. It guides safe merges by ensuring teammates understand the exact scope and constraints before integrating changes.

How do I document branch scope for collaborative development?

You document branch scope for collaborative development by drafting or updating the active intent record using the fstack-brain intent write command, specifying the Title, Body, Promises, and Not touching fields.

Can I enforce a single active intent per git branch?

Yes, you can enforce a single active intent per git branch. The intent mechanism manages exactly one current record per branch, preventing conflicting scopes and maintaining alignment across teammates during collaborative development.

What's the best way to share branch context with teammates before a merge?

The best way to share branch context is using fstack-brain workflows to read and write the active branch intent. This provides teammates with the title, body, promises, and untouched files to align work safely.

How do I update the promises and not touching fields for my current branch?

To update the promises and not touching fields for your current branch, use the fstack-brain intent write command to refine the active intent record, adjusting the scope as collaborative development requirements evolve.