skills.rest
iclinic
iclinicOFFICIAL
Explore all skills by this author →
WebsiteGitHub

design

Translate vague ideas into formal technical designs with JIRA and Figma context.

9|2|Updated Mar 12, 2026
Search Tags:#design#architecture#documentation#figma#spec#jira#phase
One-click install
npx skills add https://github.com/iclinic/afyapowers --skill design-iclinic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/iclinic/afyapowers/tree/main/src/skills/design
Command: npx skills add https://github.com/iclinic/afyapowers --skill design-iclinic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate vague ideas into formal, actionable technical designs by guiding systematic discovery, requirements elicitation, and architectural decisions, ensuring alignment before planning.

Core Features & Use Cases

  • Phase-driven design process that covers discovery, requirements, architecture, documentation, and gating to artifacts in the repository.
  • JIRA and Figma discovery integrations to enrich context with real-world constraints, scope, and design references.
  • Automated generation and storage of the design artifact, plus a spec-reviewer dispatch to validate readiness for planning.
  • Clear, iterative review flow that involves stakeholder confirmation before proceeding to the next phase.

Quick Start

Describe your feature and approve the initial design to begin the design phase.

Frequently Asked Questions about design

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

FAQPage Schema
How do I turn vague ideas into formal technical designs?▼

A formal technical design process guides systematic discovery and requirements elicitation to translate vague ideas into actionable specifications, ensuring architectural alignment before planning through structured documentation and stakeholder gating.

Can I enrich technical design context using JIRA and Figma?▼

Integrating JIRA and Figma during the discovery phase enriches technical design context by importing real-world project constraints, scope definitions, and design references directly into the architectural decision-making workflow.

What is the best way to document architecture decisions for stakeholders?▼

Documenting architecture decisions requires an iterative review flow that generates a formal design artifact, dispatches a spec-reviewer for validation, and archives gated documentation to the repository after stakeholder confirmation.

Does the technical design workflow require a spec-reviewer before planning?▼

Yes, the workflow dispatches a spec-reviewer to validate the generated design artifact for readiness, ensuring formal architectural standards are met before proceeding to downstream planning phases.

When do I need a phase-driven process for technical documentation?▼

A phase-driven process is necessary for design-heavy projects requiring structured discovery, systematic requirements elicitation, and architectural decision-making to ensure strict alignment before initiating the planning phase.

Related Skills

Explore More Design & Creative Skills→
AcendasAcendas
2

ship-discuss

Guides feature discovery conversations from vague ideas to structured plans and specs.

Official
Advanced
efekrbasefekrbas
41

design-orchestration

Route design work through brainstorming, review, and approval before implementation.

Community
Advanced
purefunctionspurefunctions

do-grill-with-docs

Validates design decisions against ADRs and CONTEXT.md during interactive Q&A sessions.

Community
Intermediate
Brennan-WilkersonBrennan-Wilkerson

capture

Parse screenshots, notes, and text into structured contacts, tasks, and ideas for Supabase storage.

Community
Advanced