Menü
Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Active token optimization and context efficiency specialist. ALWAYS trigger when the user asks about reducing Claude costs, saving tokens, running out of context, context window full, making Claude faster, optimizing prompts, which model to use, when to use Haiku vs Sonnet vs Opus, when to compact, or how to get more from Claude. Also triggers for: 'Claude is getting slow', 'context is getting long', 'how do I use Claude efficiently', 'save tokens', 'reduce API cost', 'which model should I use for this', 'prompt is too long'. Works alongside token-tracker for cost monitoring.
Token usage tracking and cost monitoring specialist. ALWAYS trigger when the user asks about token usage, API cost, token count, input/output tokens, billing, cost tracking, cost estimate, how much did this cost, token monitoring, usage stats, or wants to see how many tokens a request used. For active optimization strategies (model selection, context management, prompt efficiency) use token-optimizer instead.
CTO-level engineering leadership advisor. Invoke for strategic and organisational decisions: technology strategy, engineering roadmap planning, build vs buy analysis, technical debt triage, team structure and hiring, engineering culture, DORA metrics, OKRs for engineering, vendor/platform evaluation, make-or-buy decisions, architecture governance, incident review process, engineering blog strategy, and first 90 days as a new CTO/tech lead. NOT for writing code — for implementation use the relevant stack skill.
Platform engineering and SRE specialist. Invoke for: GitOps with ArgoCD/Flux, multi-cluster Kubernetes management, platform engineering principles (Internal Developer Platforms), incident response runbooks, SLA/SLO/SLI definitions, observability strategy (metrics/traces/logs), on-call procedures, chaos engineering, disaster recovery planning, FinOps/cloud cost optimization. For standard Docker/CI/CD pipeline setup use devops-cicd instead.
Advanced Flutter architecture specialist. Use for Flutter architecture decisions, NOT standard Flutter implementation (use flutter-dev for that). Invoke for: Flutter clean architecture, feature-first project structure, advanced Riverpod patterns (Notifier/AsyncNotifier/family), advanced Bloc (Cubit vs Bloc tradeoffs, BlocObserver), Flutter performance profiling (DevTools, shader compilation, jank), custom RenderObject, platform channels/MethodChannel, multi-module monorepo, Flutter plugin authoring, isolates/compute(), build_runner code generation, get_it/injectable DI, Flutter 3.x upgrade migrations.
Use when building Laravel 11+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
| 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