scoping-design-tasks

Coordinate design and planning task scoping to produce actionable Design Briefs.

Updated Aug 18, 2025
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill scoping-design-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scoping-design-tasks
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/scoping-design-tasks
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill scoping-design-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Defines the scope and direction for design and planning tasks (ADRs, System Context, Specs). Coordinates reconnaissance and analysis to produce a Design Brief that guides subsequent creation skills.

Core Features & Use Cases

  • Role Definition: You are a Design Strategist who clarifies requirements and surfaces decision inputs to solidify architecture and design direction.
  • Workflow Overview:
      1. Reconnaissance Phase to gather existing design context, gaps, and constraints.
      1. Analysis Phase to perform 5W1H, Gap analysis, and generate design options.
      1. Dialogue Phase to reference the dialogue guide, surface points of debate, and elicit user decisions.
      1. Design Scoping Phase to draft a Design Brief using the provided template.
      1. Final Audit to validate the brief with audit templates and render a GO/NO-GO decision.
  • Output: Produces an actionable Design Brief that can be handed to downstream creation skills, supported by audit checklists and references.

Quick Start

Start by initiating the Reconnaissance Phase to gather the current design context and constraints, then progress through the defined workflow to produce a Design Brief.

Extra Context (optional guidance)

The skill leverages on-demand resources in assets/ (design brief template and audit checklists) and references/dialogue-guide.md to drive structured decision-making.

Frequently Asked Questions about scoping-design-tasks

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

FAQPage Schema
How do I scope design tasks to produce an actionable design brief?

To scope design tasks, coordinate reconnaissance and analysis phases to gather context and perform gap analysis. Then use a dialogue guide to elicit decisions, drafting a design brief from a template to guide reliable builds.

What is the best way to write an Architecture Decision Record for system context?

Writing an Architecture Decision Record for system context requires applying defined scope across analysis and dialogue phases. This surfaces decision inputs and generates design options to solidify architecture direction and align with user needs.

How do design brief templates support decision-making during project planning?

Design brief templates support decision-making by providing a structured format to document 5W1H analysis, constraints, and debate points. This ensures audit-ready outputs and renders a clear GO or NO-GO decision for downstream creation.

Can I use this scoping process without prior system context or specifications?

Using this scoping process without prior system context triggers the reconnaissance phase. This phase actively gathers existing design context, identifies gaps, and surfaces constraints to establish clear direction before generating specifications.

When should I not use a design strategist workflow for task scoping?

You should not use a design strategist workflow for task scoping when your project lacks downstream creation phases. The process relies on producing a design brief to hand off to subsequent creation skills, rendering it ineffective for isolated, immediate execution tasks.