Invoke when the user introduces a new requirement or changes a previous understanding of a requirement — clarifies, updates remote issues, and revises the active plan.
Installs into .claude/skills of the current project.
Are you the author of New Requirement?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/natb1-new-requirement)
---
name: new-requirement
description: Invoke when the user introduces a new requirement or changes a previous understanding of a requirement — clarifies, updates remote issues, and revises the active plan.
---
# New Requirement
Invoke whenever the user revises a previously-understood requirement — in a dispatched session or a free-form session on a feature branch.
## Steps
1. **Clarify.** Ask any questions needed to fully understand the change. Use `AskUserQuestion` when the revision has multiple reasonable interpretations. Skip if the change is unambiguous.
2. **Update remote issues.** If the change affects requirements captured in GitHub issues (primary, parent, sibling, sub-issue, blocker), edit them so the remote record matches the new understanding. Use `gh issue edit <num> --body '...'` or `gh issue comment <num> --body '...'`. Touch only affected issues; list them to the user first if ambiguous.
3. **Revise the active plan.** If a plan is active for the current work (plan mode, or a tracked task list), review each step against the revised requirement. Update steps that no longer apply; remove steps that are now obsolete; add new steps the revision introduces. If no plan is active, skip.
