Mint a new REQ ID in the Assured project's namespace, with module assignment, and append it to the requirements-spec.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill when adding a new requirement to an existing requirements-spec under the Assured bundle. Computes the next sequential ID for the feature and module, prompts for the requirement text, and appends a properly-formatted ### REQ-... section.
<feature-id> (or <module-id> for positional projects): which spec to append toLocate the requirements-spec. Read docs/specs/<feature-id>/requirements-spec.md. If the project uses positional decomposition, read the spec for the matching module.
Compute the next REQ number. Scan existing ### REQ-... headings. New ID is the max + 1, zero-padded to 3 digits.
Prompt for the requirement text. Ask: "Single declarative sentence describing the new requirement?"
Append the section.
### REQ-<feature-id>-<NNN>
<text>
**Module:** <module-id>
Confirm. Show the diff to the user before saving.
Save. Write the file.
Remind. "Next steps: add a corresponding DES in design-spec.md (use req-link), then a TEST in test-spec.md."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.
The English summary is being prepared. Showing the original description.
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
The English summary is being prepared. Showing the original description.
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
The English summary is being prepared. Showing the original description.
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
The English summary is being prepared. Showing the original description.
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
The English summary is being prepared. Showing the original description.
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
The English summary is being prepared. Showing the original description.