escalators-not-stairs

Review user stories for mandatory requirements and requirement downgrades.

2|1|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/neozenith/agentic-dotfiles --skill escalators-not-stairs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: escalators-not-stairs
Source: https://github.com/neozenith/agentic-dotfiles/tree/main/skills/escalators-not-stairs
Command: npx skills add https://github.com/neozenith/agentic-dotfiles --skill escalators-not-stairs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent the erosion of user requirements during software development by ensuring that every requirement is treated as mandatory before considering fallback options.

Core Features & Use Cases

  • Requirement Enforcement:强制执行每个用户需求的正确实现,确保没有遗漏。
  • Plan Review:审查计划和实现,以检查是否存在要求侵蚀,即明确定义的要求被无声地降级为可选/备用/跳过带警告模式。
  • Use Case:在使用LLM进行软件设计和规划时,这个技能可以帮助开发团队确保所有关键功能都得到妥善处理。

Quick Start

Run the "escalators-not-stairs" skill to check if a user story includes all mandatory requirements without any degradation paths.

Frequently Asked Questions about escalators-not-stairs

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

FAQPage Schema
How do I prevent user requirement erosion during software planning?

To prevent user requirement erosion, review user stories to enforce mandatory implementation and block silent downgrading of critical needs to optional fallback strategies during early-stage software planning.

What is requirement erosion in user story planning?

Requirement erosion in user story planning occurs when explicitly defined mandatory requirements are silently downgraded into optional, skipped, or fallback modes during the software design process.

How do I check if a user story includes all mandatory requirements?

Check user stories by running a requirement review to ensure every user need is treated as mandatory and implemented correctly, verifying no fallback paths or skip-with-warning modes exist.

Can I enforce mandatory implementation for all features in a user story?

Yes, you can enforce mandatory implementation by reviewing plans to ensure every user need is implemented correctly without fallback strategies, preventing any silent downgrading of requirements.

When should I review software plans for requirement downgrading?

Review software plans for requirement downgrading during early-stage project planning and requirement definition, ensuring critical functionality is handled before implementation begins.