extract-requirements-from-mock
Translates HTML mock designs into structured documentation of user-facing requirements.
Install
mkdir -p .claude/skills/extract-requirements-from-mock && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12217" && unzip -o skill.zip -d .claude/skills/extract-requirements-from-mock && rm skill.zipInstalls to .claude/skills/extract-requirements-from-mock
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Extract requirements document from HTML mock iterationKey capabilities
- →Locate a specific feature folder using the provided feature name
- →Gather context from `mocks.context.md` and `mocks.html` files
- →Extract user-facing requirements from mock iteration sessions
- →Create a structured requirements document in markdown format
- →Present the extracted requirements for user review
How it works
The skill locates a feature folder, reads context from mock files, and then extracts user-facing requirements to create a structured markdown document.
Inputs & outputs
When to use extract-requirements-from-mock
- →Create requirements document from mocks
- →Define system behavior
- →Document UI requirements
About this skill
Extract Requirements from Mock
You are extracting a clean requirements document from an HTML mock iteration session.
Input
Feature name: $ARGUMENTS
Steps
-
Locate the feature folder: Look for
docs/$ARGUMENTS/- If it doesn't exist, ask the user to provide the correct feature name
-
Gather all context:
- Read
mocks.context.mdfor the original description, Q&A, and all logged UI tweaks - Read
mocks.htmlto understand the final UI state - Review the conversation history for any additional context
- Read
-
Extract requirements: Create
docs/$ARGUMENTS/requirements.mdwith:- Focus only on user-facing behavior - what the user sees and can do
- No implementation details - don't specify how things should be built
- No acceptance criteria - just describe the behavior
-
Structure the requirements doc:
# <Feature Name> - Requirements This document specifies the user-facing requirements for <feature>. It describes *what* the system must do from the user's perspective. --- ## 1. <First Major Area> - **REQ-XXX-1:** <requirement> - **REQ-XXX-2:** <requirement> ## 2. <Second Major Area> ... -
Present the requirements to the user for review.
-
Optionally regenerate mocks: Ask the user if they would like to:
- Rename the old mocks and regenerate fresh ones based on the new requirements
- Keep the existing mocks as-is
When not to use it
- →When the goal is to define implementation details
- →When the goal is to specify acceptance criteria
- →When the feature folder does not exist
Limitations
- →It focuses only on user-facing behavior
- →It excludes implementation details
- →It does not include acceptance criteria
How it compares
This workflow automates the extraction and structuring of requirements from mock files, unlike manually sifting through mock iterations and writing documentation.
Compared to similar skills
extract-requirements-from-mock side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| extract-requirements-from-mock (this skill) | 0 | 4mo | No flags | Beginner |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by imbue-ai
View all by imbue-ai →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.