mine.design

Scope requirements, investigate codebases, and generate formal design documents.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mine.design
Source: https://github.com/NodeJSmith/Claudefiles/tree/main/skills/mine.design
Command: npx skills add https://github.com/NodeJSmith/Claudefiles --skill mine-design

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill guides users through the process of designing software changes, from initial scoping to a signed-off design document, ensuring alignment with project goals and technical constraints.

Core Features & Use Cases

  • Scoped Design: Investigates proposed changes, asks targeted questions, and researches the codebase.
  • Design Document Generation: Creates structured design documents based on research and user input.
  • Gatekeeping: Ensures user sign-off before proceeding to implementation planning.
  • Use Case: You have a new feature idea. Use this Skill to scope it, research its feasibility in the existing codebase, write a formal design document, and get approval before writing any code.

Quick Start

Use the mine.design skill to design a new rate limiting feature for the API.

Frequently Asked Questions about mine.design

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

FAQPage Schema
How do I create a formal software architecture design document for a new feature?

To create a software architecture design document, you scope the proposed changes, investigate the existing codebase via sub-agents, and conduct targeted Q&A to generate a structured design document. This ensures the proposed software changes align with project goals before implementation planning.

What's the best way to scope requirements and investigate codebase feasibility before coding?

Scoping requirements and investigating codebase feasibility involves researching the existing code structure and asking targeted architecture questions to validate the design. This proportional investigation approach ensures your software design is grounded in the actual technical constraints of the project.

Does this software design process gate on user approval before proceeding to implementation?

Yes, the software design process gates on user approval before proceeding to implementation planning. It validates the generated design document against the project constitution and requires explicit user sign-off to ensure alignment with technical constraints.

Can I validate proposed software changes against a project constitution during design?

You can validate proposed software changes against a project constitution during the design phase. The workflow checks the generated design document for compliance with established project goals and technical constraints before allowing the process to advance.

When do I need a formal design document for software architecture changes?

You need a formal design document for software architecture changes when a new feature requires scoping and codebase investigation before coding. It provides a structured record of the research, Q&A, and proportional architecture decisions needed to ensure technical alignment.

How does codebase investigation work during the software design scoping process?

Codebase investigation during software design scoping works by deploying sub-agents to research the existing code structure. This automated investigation gathers the technical context needed to ask targeted architecture questions and generate a feasible design document.