scope-definition
Skill3 starsChanged 3 months agoApache-2.0View on GitHub
Compatibility name for the scope interview within Architectural Alignment. Use for older Scope Definition requests or reroutes in an explicitly requested Bearing lifecycle. Do not run as a separate stage, agent, or repeated interview.
In this repository15 other files it gives its agents.
- architectural-alignmentSkill
- bearing-liteSkill
- coordinatorSkill
- implementerSkill
- intakeSkill
- integration-engineerSkill
- light-implementerSkill
- onboard-bearingSkill
- planning-and-designSkill
- promptSkill
- requirements-engineerSkill
- reviewerSkill
- scribeSkill
- systems-modelerSkill
- test-engineerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use Architectural Alignment and Scope.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scope Definition — Compatibility Name
Use Architectural Alignment and Scope. It owns architecture context, the scope interview, and the final decision batch. Continue the existing Orchestrator controller session; do not dispatch an agent or rerun completed work. Planning and Design is next once the combined stage has current evidence and confirmed material intent.
Legacy REROUTE_SCOPE_DEFINITION routes to that same combined stage. Reuse its
confirmed decisions; this name never adds a second stage or invocation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.