skills.rest
jokerman89
jokerman89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

li-scope

Defines initiative boundaries, dependencies, and planning depth for repository workflows.

Updated May 27, 2026
Search Tags:#workflow#planning#scoping#dependencies#agent skills#github copilot#lintel
One-click install
npx skills add https://github.com/jokerman89/lintel --skill li-scope-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: li-scope
Source: https://github.com/jokerman89/lintel/tree/main/.github/skills/li-scope
Command: npx skills add https://github.com/jokerman89/lintel --skill li-scope-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start implementation without clear boundaries, leading to scope creep and mismatched planning effort. This Skill establishes what an initiative includes, what it depends on, and how deeply it should be planned before any build work begins. ## Core Features & Use Cases - Boundary Definition: Establishes the explicit scope of an initiative so work stays focused and reviewable. - Dependency Mapping: Identifies dependencies that affect sequencing and planning decisions. - Planning Depth Selection: Determines the appropriate level of planning detail for the size of the request. - Use Case: Before asking your Copilot agent to implement a new feature, run the scope workflow to produce a bounded definition with dependencies, which then feeds into plan and build card generation. ## Quick Start Ask your Copilot agent to scope the initiative by describing the feature or change you want bounded before planning begins.

Frequently Asked Questions about li-scope

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

FAQPage Schema
How do I define project scope before planning with GitHub Copilot?▼

Invoke the li-scope skill in your Copilot client with a description of the initiative. It loads the canonical scope workflow, which produces boundaries, dependencies, and a recommended planning depth written to your working repository.

What does the li-scope skill produce as output?▼

It produces a scoped definition of the initiative covering boundaries, dependencies, and planning depth. Outputs are written to the working repository following the adapter's tool mapping, authorization, and verification rules.

When should I run scoping before creating an implementation plan?▼

Run scoping whenever an initiative lacks clear boundaries or its dependencies are unknown. It is the entry point of the Lintel workflow, preceding plan generation and build card execution.

Does li-scope work outside the Lintel repository workflow?▼

No. It depends on the Lintel structure, specifically the Copilot adapter contract and the canonical scope skill located in the repository's skills directory. It must be installed as part of the Lintel kit.

Why does li-scope reference another SKILL.md file?▼

It is a thin adapter that delegates to a canonical scope workflow shared across agent clients. This keeps one source of truth for the workflow while letting each client apply its own tool mapping and authorization rules.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

docs-project-brief

Define project context, problem statement, and MVP boundaries.

Community
Basic
cromesdkcromesdk

project-planner

Generate deterministic project plans with scope, milestones, WBS, dependencies, and critical path.

Official
Advanced
manuscomanusco

resonance-ops-core

Initializes project scaffolds and maintains file-based state and memory across sessions.

Community
Advanced
chenziyang110chenziyang110

sp-implement-teams

Execute spec-kit implementation tasks through Claude Code Agent Teams with shared task ledgers.

Community
Advanced