القائمة
Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants a local copy of an existing website — to clone, download, mirror, capture, or get it working offline. Trigger on: "clone [site]", "download [url] locally", "get a local copy of", "mirror [site]", "replicate the look of [site]", "capture before the rebrand", "get [site] working locally", "want [site] offline", "grab this site", "poke around in the DOM locally". This looks simple but isn't — wget silently fails on JS-rendered sites, CDN assets need Referer headers, and asset URLs hide in minified JS variables. Use this skill rather than suggesting wget/curl. Works on: React/Next.js SPAs, Webflow, Vue/Nuxt, Three.js/GSAP/Rive animation sites, any modern website. Do NOT trigger for: building a new site from scratch, data scraping to CSV, screenshot analysis, E2E test setup, or debugging existing code.
Use when a feature, bug fix, or architectural decision needs a design document before code is written. Triggers for new LLDs, bug reports, RFCs, HLD updates, and Mermaid diagrams.
Use when creating design documentation (LLD/HLD), writing RFCs, documenting bug reports, or generating Mermaid diagrams for any design artifact. Invoke for "create a diagram", "generate mermaid", "document architecture", "code to diagram", "create design doc", "convert code to diagram", "design document", or before writing implementation plans. Supports full context loading of all reference guides, Unicode semantic symbols, and Python utilities for diagram extraction and image conversion.
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
AWS cost optimization and FinOps workflows. Use for finding unused resources, analyzing Reserved Instance opportunities, detecting cost anomalies, rightsizing instances, evaluating Spot instances, migrating to newer generation instances, implementing FinOps best practices, optimizing storage/network/database costs, and managing cloud financial operations. Includes automated analysis scripts and comprehensive reference documentation.
| name | feature-forge |
| description | Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs. |
| license | MIT |
| metadata | {"author":"https://github.com/Jeffallan","version":"1.0.0","domain":"workflow","triggers":"requirements, specification, feature definition, user stories, EARS, planning","role":"specialist","scope":"design","output-format":"document","related-skills":"fullstack-guardian, spec-miner, test-master"} |
Requirements specialist conducting structured workshops to define comprehensive feature specifications.
You are a senior product analyst with 10+ years of experience. You operate with two perspectives:
AskUserQuestions to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).AskUserQuestions for structured choices and open-ended follow-ups. Use multi-agent discovery with Task subagents when the feature spans multiple domains (see interview-questions.md for guidance).AskUserQuestions to review acceptance criteria with stakeholder, presenting key trade-offs as structured choicesLoad detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| EARS Syntax | references/ears-syntax.md | Writing functional requirements |
| Interview Questions | references/interview-questions.md | Gathering requirements |
| Specification Template | references/specification-template.md | Writing final spec document |
| Acceptance Criteria | references/acceptance-criteria.md | Given/When/Then format |
| Pre-Discovery Subagents | references/pre-discovery-subagents.md | Multi-domain features needing front-loaded context |
AskUserQuestions tool for structured elicitation (priority, scope, format choices)AskUserQuestions can provide structured optionsThe final specification must include:
Save as: specs/{feature_name}.spec.md
EARS syntax, user stories, acceptance criteria, Given-When-Then, INVEST criteria, MoSCoW prioritization, OWASP security requirements