Agent skill

042-planning-openspec

Use when you need to take a `*.plan.md` file and turn it into OpenSpec change artifacts by validating OpenSpec installation, initializing or reusing an OpenSpec project, and creating or updating a change proposal/spec/tasks flow. Includes a concrete workflow based on `examples/requirements-examples/problem1/requirements/openspec`. Part of the skills-for-java project

View SKILL.md on GitHub Repository
Stars 350
Forks 63

Install this agent skill to your Project

npx add-skill https://github.com/jabrena/cursor-rules-java/tree/main/skills/042-planning-openspec

Metadata

Additional technical details for this skill

author
Juan Antonio Breña Moral
version
0.14.0

SKILL.md

OpenSpec Change Planning from *.plan.md

Guide the process of turning an implementation plan (*.plan.md) into an OpenSpec change workflow. This is an interactive SKILL. It verifies CLI availability, initializes OpenSpec when needed, and then creates or updates a change with proposal, design, tasks, and spec deltas.

What is covered in this Skill?

  • Input analysis from *.plan.md (scope, change-id candidate, affected capabilities)
  • Installation and availability checks for OpenSpec CLI
  • Recommended installation paths on macOS, Linux, and Windows using npm
  • OpenSpec project bootstrapping with openspec init
  • Existing-project workflow using openspec list, openspec status, openspec show
  • Validation and completion flow with openspec validate --all and openspec archive
  • Example-root workflow at examples/requirements-examples/problem1/requirements/openspec

Constraints

Always execute OpenSpec commands from the parent directory that contains the openspec/ folder. Do not invent requirements not present in the *.plan.md; convert plan intent into explicit OpenSpec change artifacts.

  • MUST: Start by reading and summarizing the provided *.plan.md
  • MUST: Check CLI availability with openspec --version before any OpenSpec operation
  • MUST: If OpenSpec is missing, provide macOS, Linux, and Windows install guidance via npm command
  • MUST: Offer openspec init when no OpenSpec project exists
  • MUST: When creating a new OpenSpec project, run plain openspec init only (do not use --tools ... options)
  • MUST: Use a stable change-id (for example: add-dark-mode) for status/show/archive commands
  • MUST: Run openspec validate --all before archiving
  • MUST: When a feature/change is completed (all checklist tasks done), guide the user to archive it (for example: openspec archive us-001-god-analysis-api)
  • MUST: In tasks.md, generate a single OpenSpec checklist (- [ ] / - [x]) only; do not add a second table-based task list
  • MUST: Explain whether the workflow creates a new change or updates an existing one

When to use this skill

  • Convert *.plan.md into OpenSpec
  • Add change proposal from plan
  • Update existing OpenSpec project
  • Initialize OpenSpec in requirements folder
  • Validate and archive OpenSpec change

Reference

For detailed guidance, examples, and constraints, see references/042-planning-openspec.md.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

jabrena/cursor-rules-java

513-frameworks-micronaut-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

014-agile-user-story

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

502-frameworks-micronaut-rest

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

114-java-maven-search

Covers Maven Central search (Search API, maven-metadata.xml, artifact URLs) and project-local update reports via versions-maven-plugin (display-property-updates, display-dependency-updates, display-plugin-updates). Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply to the user’s pom.xml. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

323-frameworks-spring-boot-testing-acceptance-tests

Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires .feature file in context. Part of the skills-for-java project

350 63
Explore
jabrena/cursor-rules-java

200-agents-md

Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. Part of the skills-for-java project

350 63
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results