lightforgelabsstudio/scope
skills/scope/SKILL.md
Decompose an accepted spec (and its ADR, if one exists) into GitHub issues using the issue-creator tool.
tools
Updated Jun 12, 2026
$ install --global
skillsauthnpx skillsauth add lightforgelabsstudio/aide scopeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 7:38 AM129.6s1 file scanned
SKILL.md
- name:
- scope
- description:
- Decompose an accepted spec (and its ADR, if one exists) into GitHub issues using the issue-creator tool.
Scope
Turn an accepted system spec into a set of GitHub issues. Read AGENTS.md if not in context.
Inputs
Path to the accepted spec in docs/specs/ (or paste contents). If the design produced an ADR, read it too. Optionally: repo override (owner/repo).
Workflow
-
Read the spec (and ADR if present) — Extract: the change being made, Invariants affected, Success Criteria, and any explicit scope boundaries.
-
Identify work units — Break the decision into discrete, independently deliverable chunks. Each chunk becomes one issue.
-
Write spec file — Create a temporary spec in issue-creator batch format:
## Epic: <title> Goal: <from the spec's design/change section> Spec: <path-to-spec> (plus ADR path if one exists) ### Issue: <title> Goal: <what this chunk delivers> Success Criteria: - <measurable criterion> Non-Goals: <explicit exclusions> -
Run issue-creator — Execute:
python .aide/tools/issue-creator/issue-creator.py <spec-file> -
Verify — Confirm each issue was created with correct labels and GitHub Issue Type. Output issue URLs.
-
Cleanup — Delete the temporary spec file.
Reference
- Issue-creator format + errors:
.aide/docs/agents/issue-creator-ref.md - Full tool docs:
.aide/tools/issue-creator/README.md
Related Skills
lightforgelabsstudio/sanity-check
testing
VerifiedTrustedCommunity
Skeptical gap analysis for issues, ADRs, plans, and docs. Use when the user wants a second-pass check for missing decisions, contradictions, edge cases, hidden dependencies, scope drift, or readiness before implementation.
SKILL.mdUpdated May 11, 2026
lightforgelabsstudio/sync
tools
VerifiedTrustedCommunity
Sync branch with remote and confirm a clean end-of-session state.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/skill-author
testing
VerifiedTrustedCommunity
Create or update an AIDE skill in .aide/skills with valid frontmatter and a concise workflow.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/respond
documentation
VerifiedTrustedCommunity
Apply findings from a /findings review to a spec or ADR and write a response file
SKILL.mdUpdated May 7, 2026