swe-workflow-detect-req

Extract explicit and implicit requirements from user requests into WORKING_MEMORY.

1|Updated Jan 16, 2026

Search Tags:#workflow #planning #specification #requirements #analysis #edge-cases

Ready to run

npx skills add https://github.com/EarthmanWeb/serena-workflow-engine --skill swe-workflow-detect-req

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swe-workflow-detect-req
Source: https://github.com/EarthmanWeb/serena-workflow-engine/tree/main/skills/swe-workflow-detect-req
Command: npx skills add https://github.com/EarthmanWeb/serena-workflow-engine --skill swe-workflow-detect-req

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically identifies both explicit requirements and the implicit considerations that surround a user request, helping teams capture complete scope and reduce miscommunication.

Core Features & Use Cases

Explicit requirement extraction: parses user text to surface stated needs.
Implicit need inference: detects edge cases, validation rules, and non-functional considerations that are not stated outright.
Documentation & tracking: writes findings to WORKING_MEMORY for traceability and future reference.
Use Case: during feature discovery or planning sessions, feed a user request and obtain a structured requirements brief.

Quick Start

Provide a user request and let SWE extract explicit and implicit requirements.

Frequently Asked Questions about swe-workflow-detect-req

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

FAQPage Schema

How do I extract implicit requirements and edge cases from a user request?▼

To identify implicit requirements and edge cases from user requests, use an automated requirement extraction tool to parse text and infer unstated validation rules. This surfaces non-functional considerations and categorizes needs for improved task specification.

What is the best way to document functional and non-functional requirements during feature discovery?▼

The best way to document functional and non-functional requirements during feature discovery is to parse user input and record structured findings to a persistent memory workspace. This ensures traceability and reduces miscommunication by capturing explicit and implicit considerations.

How does automatic requirement specification handle integration needs and validation rules?▼

Automatic requirement specification handles integration needs by detecting unstated dependencies within user requests. It categorizes these implicit considerations alongside functional requirements to provide a structured brief for planning sessions.

Can I use requirement analysis to surface edge cases in planning sessions?▼

Yes, you can use requirement analysis to surface edge cases in planning sessions by feeding a user request into the workflow. It identifies unstated non-functional considerations and writes them to working memory for future reference.

Why do I need to detect implicit considerations for task specification?▼

You need to detect implicit considerations for task specification to reduce miscommunication and capture complete project scope. Identifying unstated edge cases ensures that all functional, non-functional, and integration needs are documented.