| name | intent-maintainer |
| description | Use before modifying an existing project, feature, document, architecture, or workflow when prior intent may exist. Compares a new request against stored intent files, detects drift, recommends whether to proceed, clarify, update intent, split scope, or reject the change. |
Intent Maintainer Skill
Purpose
Maintain intent across sessions by using durable intent files as the source of truth.
Where to look
Before substantial work, inspect:
docs/intent/
docs/intent/project-intent.md
docs/intent/product-intent.md
docs/intent/feature-intents/
docs/intent/intent-log.md
If no intent files exist, use the intent-clarifier skill before proceeding.
Workflow
1. Locate controlling intent
Find the most relevant intent file for the user's request. Prefer the most specific feature intent over the product or project intent.
2. Compare the new request
Check whether the request changes:
- Primary user
- Desired outcome
- Problem being solved
- Decision supported
- Scope
- Constraints
- Success criteria
- Required context
- Risk posture
- Human review rules
3. Classify alignment
Use:
- Aligned: request fits existing intent.
- Extension: request adds compatible scope.
- Drift: request changes purpose, user, scope, or success criteria.
- Conflict: request violates constraints or success criteria.
- Unknown: not enough information to compare.
4. Decide action
- Aligned: proceed and mention the controlling intent briefly.
- Extension: recommend adding to the intent file or roadmap.
- Drift: pause and ask whether to update intent, treat as future phase, or create separate intent.
- Conflict: do not proceed until resolved.
- Unknown: ask a minimal clarification question.
5. Update the durable record
When intent changes, update the relevant intent file and append to docs/intent/intent-log.md.
Log:
- Date
- Area / feature
- Decision
- Reason
- Superseded intent, if any
- Owner / requester
6. Guard against scope creep
If a request expands a simple MVP into a larger product, flag it.
Example:
This appears to expand the original intent from a simple compliance tracker into a broader LMS. I recommend treating this as a future phase unless you want to revise the controlling intent.
7. Final review
Before finishing, compare the completed work to the controlling intent and state any unresolved gaps.
