cursor-rules-agile
Review https://github.com/jabrena/cursor-rules-java to use this set of features
Install / Use
npx skills add jabrena/cursor-rules-agileInstalls into whichever agent you are using.
.cursorrules
Cursor IDE rules (legacy)
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of cursor-rules-agile
cursor-rules-agile scores 68/100 on our quality scale, 3870th of 4,617 Development & Engineering skills we index.
Its .cursorrules is 7.5 KB long, well organised into 10 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
It has 6 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated about 17 months ago. Expect some instructions to reference tool versions or APIs that have since changed.
- Our last check on 2026-10-20 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 75/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
cursor-rules-agile compared with similar skills
All 4 of these similar skills score higher than cursor-rules-agile; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cursor-rules-agile (this skill)by jabrena | 68 | 6 | 17mo ago | .cursorrules |
| taste-skillby Leonxlnx | 100 | 110.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 109.2k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 69.8k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 46.6k | 2d ago | CLAUDE.md |
Frequently asked questions
- How do I install cursor-rules-agile?
- Run
npx skills add jabrena/cursor-rules-agile. The install tabs above show the steps for each supported agent. - Which AI agents does cursor-rules-agile work with?
- It is written for Cursor, as a .cursorrules file. Other agents that read the same format can often use it too.
- Is cursor-rules-agile safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 75/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is cursor-rules-agile still maintained?
- The repository was last updated about 17 months ago. Expect some instructions to reference tool versions or APIs that have since changed.
Skill content
View source on GitHubCursor rules for Agile
Motivation
Using modern IDEs with AI capabilities like Cursor, software engineers can use those features to implement software using prompts. However, in order to help the models, it is a good idea to provide the software requirements, technical decisions, and designs in context.
Using conversational and non-conversational approaches, you can decompose your problems into EPICs, Features & User Stories if you follow Agile principles. With that analysis, you can answer the questions about What you are going to build, Why it is necessary to build, and Who is going to use the software. Apart from those questions, you should describe the technical specifications about How you will implement the software, and you can describe those restrictions using ADR files as the format to describe the functional and non-functional requirements. You can also model the design using diagrams in UML & C4 format.
Models using specifications, decision records, and diagrams in context will generate better software with less ambiguity and less waste.
Goals
This repository provides a set of cursor rules to generate good software specifications based on Agile principles to be added to the Cursor context to generate better software.
The repository can be used by the following roles: EA, PO, BA, SA, TL, SSE, SE
https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/define-features-epics?view=azure-devops&tabs=agile-process
Cursor Rules
Cursor rules designed to answer the questions about WHAT the development team is going to build, WHY it is necessary to build, and WHO is going to use it:
| Phase | Role | Cursor Rule | Description | |-------|------|-------------|-------------| | Software requirements gathering | Product Owner | Create an Agile Epic | Define and structure high-level business objectives as epics | | Software requirements gathering | Product Owner | Create an Agile Feature | Break down epics into manageable features | | Software requirements gathering | Product Owner / Business Analyst | Create an Agile User Story | Create detailed user stories from features with acceptance criteria based on Gherkin |
Cursor rules designed to answer the questions about HOW the team is going to build the requirements and WHAT restrictions the software will have:
| Phase | Role | Cursor Rule | Description | |-------|------|-------------|-------------| | Design | Solution Architect | UML Sequence Diagram | Generate UML sequence diagrams to visualize system interactions | | Design | Solution Architect | C4 Model Diagrams | Create C4 architecture diagrams for system visualization | | Requirements | Solution Architect / Technical Lead | ADR about Functional requirements for CLI Development | Create architectural decision records about functional requirements for CLI applications | | Requirements | Solution Architect / Technical Lead | ADR about Functional requirements for REST API | Create architectural decision records about functional requirements for REST API development | | Requirements | Solution Architect / Technical Lead | ADR about Acceptance Testing Strategy | Define comprehensive acceptance testing strategies | | Requirements | Architect / Technical Lead | ADR about Non-Functional Requirements | Define non-functional requirements and constraints following ISO-25010 | | Requirements | General | ADR creation using a Conversational approach | Interactive assistant for creating architectural decision records |
Cursor rules designed to implement the requirements and refactor:
| Phase | Role | Cursor Rule | Description | |-------|------|-------------|-------------| | Implementation | Product Owner / Technical Lead | Create Task List | Generate detailed task lists from agile artifacts | | Implementation | Technical Lead / Senior Software engineer | Implement Task List | Manage and track implementation of generated tasks | | Implementation | Product Owner / Technical Lead | Definition of Done Creation | Create comprehensive Definition of Done documents with quality gates and completion criteria | | Refactoring | Technical Lead / Senior Software engineer | UML Class Diagram Generator | Generate UML class diagrams for object-oriented design |
Getting Started
If you are interested in getting the benefits from these cursor rules, you can manually download this repository and copy the './cursor' folder and paste it into your repository, or delegate this task to a specific command-line tool based on Jbang:
sdk install jbang
# Add cursor rules for Agile in ./cursor/rules
jbang --fresh setup@jabrena init --cursor https://github.com/jabrena/cursor-rules-agile
Once you have installed the cursor rules:
| Phase | Role | Cursor Rule | Description | |-------|------|-------------|-------------| | Getting Started | All | Create Agile Development Checklist | Cursor rule designed to help the user to use the whole set of cursor rules for agile in an easy way |
Type the following prompt in the cursor chat:

Create an agile development checklist using the cursor rule @2000-agile-checklist
Examples
Learn about how these rules helped to implement some non-trivial examples
How to contribute
If you have nice ideas, please create an issue
References
- https://www.cursor.com/
- https://docs.cursor.com/context/rules
- https://docs.cursor.com/context/@-symbols/@-cursor-rules
- https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/define-features-epics?view=azure-devops&tabs=agile-process
- https://gojko.net/books/specification-by-example/
- https://cucumber.io/docs/gherkin/reference
- https://plantuml.com/
- https://www.plantuml.com/plantuml/uml/
- https://c4model.com/abstractions
- https://www.iso25000.com/index.php/en/iso-25000-standards/iso-25010
- https://www.iso.org/standard/78176.html
- https://github.com/snarktank/ai-dev-tasks
Cursor rules ecosystem
- https://github.com/jabrena/101-cursor
- https://github.com/jabrena/cursor-rules-methodology
- https://github.com/jabrena/cursor-rules-agile
- https://github.com/jabrena/cursor-rules-java
- https://github.com/jabrena/cursor-rules-spring-boot
- https://github.com/jabrena/cursor-rules-examples
- https://github.com/jabrena/cursor-rules-sandbox
- https://github.com/jabrena/plantuml-to-png-cli
- https://github.com/jabrena/setup-cli
- https://github.com/jabrena/jbang-catalog
Related Skills
taste-skill
110.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
109.2kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
69.8kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
46.6kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

