Add rule for MODIFIED/REMOVED Requirements #416

Activity

1. coderabbitai commented on Dec 28, 2025

   

   coderabbitaibot

   on Dec 28, 2025 – with coderabbitai

   Contributor

   More actions

   📝 CodeRabbit Plan Mode

   Generate an implementation plan and prompts that you can use with your favorite coding agent.

   • Create Plan

   Examples

   • Example 1
   • Example 2

   ---

   🔗 Similar Issues

   Related Issues

   • Archive command fails when creating new spec file with REMOVED Requirements #403
   • Bug: Archive validation fails despite requirement headers containing SHALL/MUST #159
   • Feature request: automatically update project.md during archive #331
   • How it resolves behavioral conflicts of different specs. #75
   • Model tends to cheat around "no deltas found error" #194

   🔗 Related PRs

   #404 - Fix: Allow REMOVED requirements when creating new spec files (#403) [merged]

   👤 Suggested Assignees

   • smileeunsong
   • PeakMNA
   • BobbyWang0120
   • SolomidHero
   • agladysh

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
2. lucidfrontier45

   added a commit that references this issue on Jan 24, 2026

   docs: add clarification on verifying modified/removed requirements in…

   ...

   b1d3904
3. pbarvinko

   added a commit that references this issue on May 13, 2026

   docs(agents): address PR review — conditional MODIFY collapse + defau…

   ...

   5d6d62c
4. clay-good commented on Jul 22, 2026

   

   clay-good

   on Jul 22, 2026

   Collaborator

   More actions

   Closing as resolved by #1326. The spec-driven schema instructions now contain exactly the rule you asked for (schemas/spec-driven/schema.yaml, MODIFIED requirements workflow):

   1. Locate the existing requirement in openspec/specs//spec.md
   2. Copy the ENTIRE requirement block
   3. Paste under ## MODIFIED Requirements and edit
   4. Ensure header text matches exactly (whitespace-insensitive)

   Archive also gained a drift guard (#1391) that aborts rather than silently dropping scenarios when blocks do not line up. Validate-time enforcement of MODIFIED headers against the base spec is tracked separately in #1112.
5. clay-good

   closed this as completedon Jul 22, 2026