Convert user stories into executable development plans with role-based workflows.
npx skills add https://github.com/ferrosasfp/wasiai-v2 --skill nexus-agil
Please help me install this Agent Skill. Skill: nexus-agil Source: https://github.com/ferrosasfp/wasiai-v2/tree/main/.claude/skills/nexus-agil Command: npx skills add https://github.com/ferrosasfp/wasiai-v2 --skill nexus-agil
NexusAgil provides a stack-agnostic, role-based process to reliably convert user stories into executable pipelines, reducing miscommunication and drift.
Describe your HU and say NexusAgil start FAST to initiate the quick flow.
High-intent search queries and answers about installing and using this skill.
You can convert user stories into executable development plans by using a role-based pipeline that guides FAST to LAUNCH to QUALITY workflows with codebase grounding and adversarial checks. This ensures consistent, auditable delivery across analysts, architects, developers, and QA.
Codebase grounding in agile workflows anchors development tasks to the actual codebase and prescribed artefacts, preventing hallucination. It enforces anti-hallucination checks and adversarial reviews through defined gates from F0 context to F4 validation.
To start a workflow using a Story File, describe your user story and initiate the quick flow. The pipeline then strictly implements the feature from the Story File using waves and anti-hallucination checks.
Yes, you can use a stack-agnostic workflow for diverse tech stacks because it defines context, constraints, and delivery steps independently of the underlying technology. This allows cross-functional teams to align without stack-specific dependencies.
The best way to enforce traceability and delivery gates across distributed teams is through a role-based orchestration pipeline that prescribes artefacts, gates, and responsibilities. This provides end-to-end processing from context to validation with auto-blindaje.
Development processes suffer from drift and miscommunication when they lack a disciplined, role-based pipeline with defined artefacts and adversarial checks. Implementing a stack-agnostic workflow with strict story files reduces this drift and aligns teams.
konglong87Convert PRD requirements into user stories with BDD acceptance criteria.
gvinokurExecute approved implementation plans into validated code with tests, lint, and builds.
hotriluanReview code changes across PRs, commits, and codebase scans.
PVPhaCreate MVP plans with scope, user stories, acceptance criteria, and task sequencing.
