Requirements Input
Analytics
Detection History
No detection history yet
- Always test AI-generated scripts in your Personal Developer Instance (PDI) or Development Instance before deploying to higher environments.
- This tool is designed for development and prototyping purposes only. Never connect directly to Production instances.
- AI-generated code should be reviewed, tested, and validated by qualified ServiceNow developers before production use.
iDevOps LLC provides this tool as a development accelerator. Users are responsible for validating all AI-generated output before production deployment.
How to Use Epic Detector
Epic Detector automatically analyzes your requirements and identifies distinct Epics, then generates refined user stories for each Epic.
- Step 1: Upload a file or enter your project requirements (minimum 50 characters)
- Step 2: Select your preferred AI model
- Step 3: Click "Detect & Refine" to start the analysis
- Step 4: Review and edit the detected Epics and their stories
- Step 5: Export results as JSON or Markdown
File Upload
You can upload requirements documents directly instead of typing them manually.
- Supported Formats: PDF, DOCX, DOC, TXT, MD
- Maximum Size: 10MB per file
- How to Upload: Drag and drop a file onto the upload zone, or click to browse
- Text files (TXT, MD) are parsed client-side for faster processing
- PDF and DOCX files are parsed server-side to extract text content
Inline Editing
Edit generated Epics and Stories directly in the application.
- Edit Epics: Click the edit button in the Epic header to modify title, description, and priority
- Edit Stories: Click the edit button on any story card to modify all details
- Editable Fields: Title, description, story points, priority, acceptance criteria
- Auto-Save: Changes are automatically saved to history for records loaded from history
- Summary Updates: Story points and counts are recalculated after edits
Best Practices for Requirements
- Be as detailed as possible - more context leads to better Epic detection
- Include user roles and their needs (e.g., "admins need to...", "customers should be able to...")
- Mention integrations, constraints, and business rules
- Describe the expected outcomes and success criteria
- Group related functionality together in your description
Epic vs Story Guidelines
Epic: A large body of work that represents a significant feature or capability. Epics typically span multiple sprints and contain multiple user stories.
User Story: A small, independent piece of functionality that can be completed within a single sprint. Stories follow the format: "As a [user], I want [feature] so that [benefit]"
FAQ
- Q: How many Epics can be detected?
A: The system will detect as many Epics as are present in your requirements. Complex projects may have 5-10+ Epics. - Q: How many stories per Epic?
A: Each Epic typically generates 3-6 user stories depending on its complexity. - Q: Can I edit the generated stories?
A: Yes! Click the edit button on any Epic or Story to modify it. Changes are saved automatically for records loaded from history. - Q: What file formats are supported?
A: PDF, DOCX, DOC, TXT, and MD files up to 10MB.
Pricing
Pay-per-use pricing for this module (usage tier only):
- Trigger: Detect Epic (analyze requirements and generate epics/stories)
- Price: $5.00 per detection