Repository navigation
epic: agent-tool-permission-alignment - Establish the canonical contract #1738
Description
Overview
Establish canonical contract for agent tool access and permissions across the repository. This epic tracks the specification and implementation of unified tool/permission governance.
Problem
Agent specifications are currently inconsistent in tool declarations and permissions, causing unpredictable execution behavior and weakening MCP security posture.
Related OpenSpec
This epic implements the agent-tool-permission-alignment specification.
Specification Documents:
What's Changing
- Define canonical tool/permission contract for agent frontmatter
- Introduce profile tiers (standard, reviewer-only, planning-only, etc.)
- Add automated validation for all agent specs
- Add CI enforcement before merge
Scope
Affected files: All agents/*.agent.md, plugins/**/agents/*.agent.md
Definition of Ready (DoR)
- Epic vision and scope clearly defined
- Success criteria and measurable outcomes documented
- High-level tasks/stories identified
- Dependencies and risks mapped
- Timeline and resource estimates provided
- Stakeholder alignment confirmed
Definition of Done (DoD)
- All child issues/stories completed
- Epic acceptance criteria met
- Epic documentation and summary updated
- Release notes and announcement prepared
- Post-launch monitoring and support plan in place
- Retrospective completed (if applicable)
Metadata
Metadata
Assignees
Type
Fields
Priority
None yet
Activity
linear-code commentedon Aug 11, 2026
LS-2445
github-actions commentedon Aug 11, 2026
✅ Template check passed after update. Thanks for fixing the issue body.
github-actions commentedon Aug 11, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
docs: Update planning docs & OpenSpec proposals with GitHub issue num…
chore: Add reports restructuring & OpenSpec coordination documentation (
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:type:epicValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.
[-]Agent-Tool Permission Contract — Canonical Tool/Permission Alignment[/-][+]epic: agent-tool-permission-alignment - Establish the canonical contract[/+]eleshar commentedon Sep 23, 2026
Superseded by #3466, part of epic #3464 (agents and skills aligned with the official AGENTS.md, Agent Skills, GitHub Copilot and Claude Code standards). The plan this issue belonged to has been replaced there. Reopen if it covers something #3464 and its children do not.
eleshar commentedon Sep 23, 2026
Reopening: this has its own planned deliverables that #3464 and its child issues do not cover, so it is not superseded. It stays open as related work to #3464, and should follow the standards decided there (AGENTS.md,
*.agent.mdfrontmatter, Agent SkillsSKILL.md, plugin marketplace distribution).