docs(design): define spawn plugin user stories

design/user-stories/us-007-build-and-release-plugin.md

@@ -0,0 +1,25 @@
+---
+type: User Story
+title: "US-007: Build and release the plugin"
+description: Give maintainers repeatable Spigot 26.2 builds, automated verification, and versioned Gitea releases.
+status: backlog
+---
+
+# US-007: Build and release the plugin
+
+As a **plugin maintainer**, I want automated builds and releases so that tested, correctly versioned plugin artifacts can be distributed consistently.
+
+## Acceptance criteria
+
+- [ ] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
+- [ ] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
+- [ ] Pushes and pull requests build and test the plugin in Gitea Actions.
+- [ ] Pull requests validate conventional commit messages.
+- [ ] CI stores a development JAR as a workflow artifact.
+- [ ] Main-branch conventional commits drive semantic versioning.
+- [ ] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
+- [ ] The build and release workflow follows the established `spigot-event-producer` project pattern where applicable.
+
+## Related
+
+- [User-story catalog](index.md)