design

Produce a technical specification from requirements analysis within the /analyze workflow.

368|98|Updated Jan 25, 2021

Search Tags:#design #architecture #documentation #specification #requirements #i18n

Ready to run

npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill design-hardisgroupcom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design
Command: npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill design-hardisgroupcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate requirements into a concrete design and a comprehensive technical specification, reducing ambiguity early in the project lifecycle.

Core Features & Use Cases

Solution Design: Outline architecture, components, interfaces, and data flows based on requirements.
Technical Specification: Produce a structured document detailing scope, constraints, acceptance criteria, and success metrics.
Knowledge Transfer: Capture rationale and design decisions to guide implementers and reviewers.

Quick Start

Draft a complete system design and spec from the provided requirements analysis.

Frequently Asked Questions about design

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

FAQPage Schema

How do I translate software requirements into a technical specification?▼

To translate software requirements into a technical specification, this Skill analyzes your provided requirements to outline solution architecture and data flows. It outputs a comprehensive document detailing scope, constraints, and acceptance criteria.

What should be included in a technical design document for a new feature?▼

A technical design document should include architecture, components, interfaces, and data flows. This Skill generates these elements alongside deliverables like files to modify, new files, i18n keys, dependencies, and risk considerations.

How does requirement analysis map to implementation files and i18n keys?▼

Requirement analysis maps to implementation by applying the /analyze workflow to identify files to modify and patterns to reuse. It explicitly specifies new files, i18n keys, dependencies, and testing approaches needed.

Can I use this to capture design rationale for knowledge transfer?▼

Yes, you can use this Skill to capture design rationale for knowledge transfer. It produces a technical specification recording design decisions and rationale, guiding reviewers and implementers through the project lifecycle.

Does the technical specification cover testing approaches and risk considerations?▼

Yes, the technical specification covers testing approaches and risk considerations. It explicitly identifies these elements within the structured deliverables to reduce ambiguity and guide the implementation phase.