skills.rest
chrisallenlane
chrisallenlaneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

scope

Explore a problem space and draft a ticket with acceptance criteria.

18|4|Updated Jan 29, 2026
Search Tags:#planning#codebase#requirements#exploration#scope#ticket#issue-tracker
One-click install
npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill scope-chrisallenlane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/chrisallenlane/claude-swe-workflows/tree/main/skills/scope
Command: npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill scope-chrisallenlane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understands and documents complex problem spaces before implementation, ensuring you have a clear ticketable plan rather than diving into code prematurely.

Core Features & Use Cases

  • Discovery: asks clarifying questions to scope the work
  • Codebase Exploration: analyzes the repository to map architecture and dependencies
  • Iterative Refinement: refines requirements with open questions and trade-offs
  • Ticket Synthesis: drafts a detailed, actionable ticket including problem statement, acceptance criteria, and scope
  • Review & Create: presents the draft for review and can create an issue in your tracker
  • Non-implementation by default: does not modify code or write production changes

Quick Start

Run the scope workflow to begin exploring a problem space and drafting a ticket.

Frequently Asked Questions about scope

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

FAQPage Schema
How do I draft precise tickets and define requirements before refactoring a codebase?▼

To draft precise tickets before refactoring a codebase, this Skill automates exploratory ticket creation by analyzing the repository, deducing problem statements, acceptance criteria, and open questions. It outputs a draft ticket ready for issue tracker integration.

What is the best way to map codebase architecture and dependencies when planning a feature?▼

The best way to map codebase architecture during feature planning is using an automated exploration workflow that analyzes your repository dependencies. It deduces technical notes and outputs a structured ticket for review rather than diving into code prematurely.

Can I automatically create issues in my issue tracker from drafted requirements?▼

Yes, you can integrate drafted requirements with an issue tracker. After the iterative refinement process produces a detailed ticket containing acceptance criteria and scope, the workflow presents it for review and can create an issue directly.

Does this ticket synthesis workflow write production code or modify my repository?▼

No, this ticket synthesis workflow does not write production code or modify your repository. It operates strictly on non-implementation by default, focusing entirely on understanding the problem space and outputting a detailed draft ticket for review.

Related Skills

Explore More Software Engineering Skills→
bradleygoldenbradleygolden
176

hex-docs-search

Search Hex package documentation across local dependencies and caches.

Community
Intermediate
maestria-comaestria-co

linear-story

Format a structured story spec into a Linear-ready issue template.

Official
Intermediate
tonombtonomb

wayfinder

Decompose high-level objectives into dependency-aware issue tracker tickets.

Community
Advanced
DynamoDSDynamoDS
2.0k

dynamo-jira-ticket

Generate structured Jira tickets for the Dynamo project from bug reports and failing tests.

Official
Intermediate