Agent skill · product strategy · aiskillstore
ghe-requirements
This skill should be used when creating, updating, linking, or versioning requirements for GitHub Elements threads. Use when user mentions requirements, specs, REQ files, or when starting feature development. Provides the requirements folder structure, versioning system, and SERENA backup protocols.
Why this skill is useful
Provides a structured requirements management system with specific folder organization and versioning protocols that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
IRON LAW: User Specifications Are Sacred THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS. 1. Every word the user says is a specification - follow verbatim, no errors, no exceptions 2. Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST 3. Never take initiative to change specifications - your role is to implement, not to reinterpret 4. If you see an error in the spec, you MUST: Stop immediately Explain the potential issue clearly Wait for user guidance before proceeding 5. No silent "improvements" - what seems like an improvement to you may break the user's intent Violation of this law invalidates all work produced. Background Agent Boundaries When running as a background agent, you may ONLY write to: The project directory and its subdirectories The parent directory (for sub-git projects) ~/.claude (for plugin/settings fixes) /tmp Do NOT write outside these locations. --- GHEREPORTS Rule (MANDATORY) ALL reports MUST be posted to BOTH locations: 1. GitHub Issue Thread - Full report text (NOT just a link!) 2. GHEREPORTS/ - Same full report text (FLAT structure, no subfolders!) Report naming: <TIMESTAMP><title or description>(<AGENT>).md Timestamp format: YYYYMMDDHHMMSSTimezone ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus REQUIREMENTS/ is SEPARATE - permanent design documents, never deleted. Deletion Policy: DELETE ONLY when user EXPLICITLY orders deletion due to space constraints. --- GHE Requirements Management Overview Requirements in GHE are versioned markdown files stored in REQUIREMENTS/ that serve as the source of truth for feature implementation. Every DEV thread MUST link to a requirements file before work begins. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/ghe-requirements