nexus_plan

Organize software requirements into a validated Nexus plan specification with EARS notation.

Updated Mar 10, 2026

Search Tags:#planning #specification #use case modeling #requirement engineering #Nexus framework

Ready to run

npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nexus_plan
Source: https://github.com/tcfialho/Herald.Ai.Skills/tree/main/skills/nexus/nexus_plan
Command: npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the complex process of building comprehensive development plans, ensuring all requirements are specified accurately and unambiguously.

Core Features & Use Cases

Complete Requirement Specification: Guides the user to define detailed, verifiable requirements using EARS notation.
Documentation Generation: Produces structured plan documents and diagrams based on the latest specifications.
Use Case Mapping: Facilitates creating and linking use cases, drill-down flows, and system invariants for thorough architecture design.
Real-world Scenario: Imagine managing a large software project with multiple teams; use this Skill to align all stakeholders with a precise, validated plan ready for implementation.

Quick Start

Use the nexus_plan skill to generate a detailed project plan based on your initial ideas and constraints.

Frequently Asked Questions about nexus_plan

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

FAQPage Schema

How do I create a Nexus /plan specification for complex software requirements?▼

To create a Nexus /plan specification, organize complex software development requirements into a formal, validated document covering architecture, use cases, and detailed, measurable terms for engineering teams.

What is EARS notation and how does it help with requirement engineering?▼

EARS notation is a structured method for requirement engineering that guides you to define detailed, verifiable requirements. It ensures all specifications are accurate and unambiguous for stakeholders.

How do I map use cases and drill-down flows for system architecture design?▼

Mapping use cases and drill-down flows involves creating and linking use cases with system invariants. This facilitates thorough architecture design and generates structured plan documents and diagrams.

Can I use iterative refinement to update an existing project plan documentation?▼

Yes, iterative refinement supports updating existing project plan documentation. The process applies validation rules and generates reports, ensuring architecture and use case specifications remain accurate.

What is the best way to align multiple teams on a large software development plan?▼

The best way to align multiple teams is using a formal specification to define detailed, measurable requirements and use cases. This generates a validated plan document ensuring all stakeholders share a precise blueprint.