Dev10x-scope

Scope software engineering problems through a phase-driven workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-scope-brave-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x-scope
Source: https://github.com/Brave-Labs/dev10x/tree/main/codex-skills/dev10x-scope
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-scope-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope complex technical problems in software engineering by providing a reusable, phase-driven scoping workflow that informs architecture decisions and documentation.

Core Features & Use Cases

  • Phase 1 Context Gathering: collect starting point, external resources, codebase exploration, and component identification.
  • Phase 2 Solution Design: follow existing patterns, apply YAGNI and SRP, craft architecture components.
  • Phase 3 Implementation Planning: order steps, reference patterns, assess risks and mitigations.
  • Phase 4 Documentation: capture decisions, diagrams, and data flows.
  • Phase 5 Review: validate against principles and incorporate corrections.

Quick Start

Follow the base scoping workflow to scope a new codebase or architectural effort.

Frequently Asked Questions about Dev10x-scope

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

FAQPage Schema
How do I scope complex technical problems for software architecture design?

To scope complex technical problems, use a phase-driven workflow covering context gathering, solution design, implementation planning, documentation, and review to inform architecture decisions across your codebase.

What is the best way to document architectural decisions and data flows?

The best way to document architectural decisions is to capture them during a dedicated documentation phase, recording decisions, diagrams, and data flows after solution design and implementation planning are complete.

How do I apply SRP and YAGNI principles when planning codebase implementation?

To apply SRP and YAGNI during implementation planning, follow existing codebase patterns, craft architecture components adhering to these principles, order implementation steps, and assess risks and mitigations.

Does this scoping workflow support ADR and ticket scoping processes?

Yes, this scoping workflow supports Architecture Decision Records (ADRs) and ticket scoping workflows by guiding context gathering, solution design, and implementation planning across research and codebase exploration.

Can I use this approach for Clean Architecture research and component identification?

Yes, you can use this approach for Clean Architecture research by gathering context, identifying components, and validating solution designs against architectural principles during the review phase.

When should I not use a phase-driven architectural scoping workflow?

You should not use a phase-driven architectural scoping workflow for highly isolated code tweaks that require no upfront research, component identification, or formal documentation of data flows and architectural decisions.