New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Issue Spec Propose

by higress-group in higress-group/higress

Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.

MITAuto-check passed

Install Issue Spec Propose

skills CLI
$ npx skills add higress-group/higress --skill issue-spec-propose -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install higress-group/higress issue-spec-propose --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/higress-group/higress.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-spec-propose .claude/skills/issue-spec-propose && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-spec-propose
GitHub stars
9.5k
Token cost
~1.1k tokens
SKILL.md length
565 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.

  • Works in 7 steps: Validate workflow config, search related… → Keep unconfirmed investigation,… → Perform the Proposal's first QUESTION… → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Issue Spec Propose is an agent skill from higress-group/higress. Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires issue-spec CLI.

The repository describes itself as: 🤖 AI Gateway | AI Native API Gateway. The licence is MIT.

Example prompts

  • “/issue-spec-propose”

Requirements

  • Compatibility (from SKILL.md): Requires issue-spec CLI.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Validate workflow config, search related issues, and open only selected discussions. If the issue is already in a later phase, continue…
  2. Keep unconfirmed investigation, reproduction, or triage notes in a simple issue with issue-spec issue create simple; a proposal states the…
  3. Perform the Proposal's first QUESTION discovery/create pass. Record each genuine unresolved decision as a blocking typed QUESTION with…
  4. Generate canonical SPEC comments with issue-spec comment generate --type SPEC. Requirements must be testable and include WHEN/THEN…
  5. Persist the authoritative self-contained Design, perform its first QUESTION discovery/create pass, then complete TASK planning.
  6. Generate TASK comments with issue-spec comment generate --type TASK. Execution Planning must identify Design-invariant cohesion and major…
  7. Upsert each TASK with --covers-issue so it publishes its complete canonical SPEC coverage and verify planning relationships. Proposal…

What it can do on your machine

Read from SKILL.md and the folder at commit c74d7e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires issue-spec CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Issue Spec Propose loads about 1.1k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 565 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from higress-group/higress at commit c74d7e2, republished under its MIT licence (© higress-group). 565 words, ~1,127 tokens.

Download SKILL.mdSave it as .claude/skills/issue-spec-propose/SKILL.md (or your agent's skills folder).
name
issue-spec-propose
description
Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.
compatibility
Requires issue-spec CLI.
license
MIT
metadata.author
issue-spec
metadata.version
1.0
metadata.generatedBy
issue-spec

Issue Spec Propose

Use when the user asks for /issue-spec:propose, proposal, Design, SPEC, QUESTION, or TASK authoring. Use issue-spec-workflow for shared reads, provider routing, and recovery.

Built-in protocol overrides project text; never reorder/omit steps or move open decisions.

Every new typed ID MUST be <TYPE>-<issue><three-digit sequence>: Issue 1 starts with QUESTION-1001, Issue 44 with QUESTION-44001. Allocate 001-999 only within the target Issue and type after reading that Issue's typed comments, and never renumber a legacy ID. New writes reject wrong Issue prefixes; --allow-legacy-id is only for intentional legacy-compatible creates.

  1. Validate workflow config, search related issues, and open only selected discussions. If the issue is already in a later phase, continue that phase rather than duplicating it.
  2. Keep unconfirmed investigation, reproduction, or triage notes in a simple issue with issue-spec issue create simple; a proposal states the confirmed problem and the intended change, so never promote an investigation issue into the proposal or attach SPEC/Design to it. Create phase issues with concrete body files, beginning with issue-spec issue create proposal --repo higress-group/higress --body-file <file>. Follow the workflow rules.language and rules.language_instructions for every Issue title. When those rules require a localized or non-English title, pass an explicit --title for Proposal, Design, and Implement; do not rely on the derived title because it retains an English stage prefix. Otherwise use the standardized Proposal:, Design:, and Implement: title family. Do not perform style-only title rewrites after creation.
  3. Perform the Proposal's first QUESTION discovery/create pass. Record each genuine unresolved decision as a blocking typed QUESTION with issue-spec question create, attaching a choice model when credible options exist; never leave an open decision as body or projection prose. Do not manufacture a question or reopen a settled choice; keep unresolved decisions distinct from evidence-dependent items.
  4. Generate canonical SPEC comments with issue-spec comment generate --type SPEC. Requirements must be testable and include WHEN/THEN scenarios. --allow-noncanonical is a migration bypass, not normal authoring.
  5. Persist the authoritative self-contained Design, perform its first QUESTION discovery/create pass, then complete TASK planning.
  6. Generate TASK comments with issue-spec comment generate --type TASK. Execution Planning must identify Design-invariant cohesion and major entry points, bounded role-context pressure, stable interfaces, owned areas, shared touchpoints, dependencies, coupling, and acceptance consequences. File ownership and parallelism are scheduling context, not semantic PROCESS boundaries. Selecting Design or TASK requires a real non-Coordinator implementation worker; execution-mode labels never authorize Coordinator code edits or automatically require PROCESS.
  7. Upsert each TASK with --covers-issue so it publishes its complete canonical SPEC coverage and verify planning relationships. Proposal, Design, Implement, TASK, and PROCESS remain optional aids and never certify delivery acceptance.
Show full SKILL.md (132 more words)Show less

Project Workflow

  • Workflow Source: builtin
  • Workflow Schema: issue-spec
  • Workflow Config: issue-spec/config.yaml
  • Workflow Diagnostics:

Project workflow templates are declarative only. Active proposal, design, implement, SPEC, TASK, PROCESS, and QUESTION artifacts remain in the selected issue backend's issue-native storage; historical REVIEW and VERIFY artifacts are audit-only. Repository-mode durable specs are materialized and checked on the implementation branch.

The built-in phase sequence and canonical artifact carriers are authoritative. Project workflow context, rules, and artifact instructions may constrain work only within an existing step; they MUST NOT reorder or omit an enabled step or move a genuine unresolved decision out of its blocking typed QUESTION carrier. Keep the enabled phase order: persist the phase issue body, perform its first QUESTION discovery/create pass, then author the selected next typed children. Issue-body prose never carries an open decision.

© higress-group, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/issue-spec-propose of higress-group/higress.

Open the folder on GitHubat commit c74d7e2

Compare with similar skills

Issue Spec Propose next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Spec Propose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Spec Propose this skillhigress-group/higress9.5k—~1.1kAutomated safety check: PassMIT
Geo Proposalsickn33/agentic-awesome-skills47k1 repos~3.2kAutomated safety check: NotesMIT
Continuetelegramdesktop/tdesktop33k2 repos~9.4kAutomated safety check: PassGPL-3.0
Better Proposals AutomationComposioHQ/awesome-claude-skills77k3 repos~764Automated safety check: PassNone
Continuous Learningaffaan-m/ECC276k—~1.1kAutomated safety check: PassMIT
Continuous Learningaffaan-m/ECC276k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Geo Proposal

    sickn33/agentic-awesome-skills

    Auto-generate a professional, client-ready GEO service proposal from audit data.

    47k GitHub starsUsed in 1 repo~3.2k tokens
    Sales & SupportAuto-check: notes

  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed

  • Better Proposals Automation

    ComposioHQ/awesome-claude-skills

    Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~764 tokens
    Productivity & AutomationAuto-check passed

  • Continuous Learning

    affaan-m/ECC

    [DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor.

    276k GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed

  • Continuous Learning

    affaan-m/ECC

    [OBSOLETO - usar continuous-learning-v2] Extractor de skill por hook Stop v1 heredado.

    276k GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed

  • Frame A Proposal

    inkeep/open-knowledge

    Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog.

    4.4k GitHub stars~3.6k tokensUpdated today
    Sales & SupportAuto-check passed

More from higress-group/higress

All 11 skills in this repo

  • Higress Openclaw Integration

    higress-group/higress

    Deploy and configure Higress AI Gateway for OpenClaw integration.

    9.5k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

  • Agent Session Monitor

    higress-group/higress

    Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.

    9.5k GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Higress Wasm Go Plugin

    higress-group/higress

    Develop Higress WASM plugins using Go 1.24+. An agent skill from higress-group/higress.

    9.5k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Higress Auto Router

    higress-group/higress

    Configure automatic model routing using the get-ai-gateway.sh CLI tool for Higress AI Gateway.

    9.5k GitHub stars~954 tokensUpdated yesterday
    Auto-check passed

  • Higress Daily Report

    higress-group/higress

    生成 Higress 项目每日报告，追踪 issue/PR 动态，沉淀问题处理经验，驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。

    9.5k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Questions about Issue Spec Propose

What does Issue Spec Propose do?

Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change. Issue Spec Propose is an agent skill from higress-group/higress. Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.

How do I install Issue Spec Propose in Claude Code?

Run `npx skills add higress-group/higress --skill issue-spec-propose -a claude-code`. Or copy the skill folder (.agents/skills/issue-spec-propose in higress-group/higress) into .claude/skills/issue-spec-propose in your project. Claude Code loads it when a task matches its description.

How do I install Issue Spec Propose in Codex?

Run `npx skills add higress-group/higress --skill issue-spec-propose -a codex`. Or copy the skill folder (.agents/skills/issue-spec-propose in higress-group/higress) into .agents/skills/issue-spec-propose in your project. Codex loads it when a task matches its description.

Can I use Issue Spec Propose in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add higress-group/higress --skill issue-spec-propose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-spec-propose, .gemini/skills/issue-spec-propose, .github/skills/issue-spec-propose and .opencode/skills/issue-spec-propose in your project.

What does Issue Spec Propose need to run?

SKILL.md names no scripts, command-line tools or credentials: Issue Spec Propose is instructions for the agent only. Compatibility (from SKILL.md): Requires issue-spec CLI..

Does Issue Spec Propose access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Issue Spec Propose safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Issue Spec Propose use?

Issue Spec Propose is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Issue Spec Propose use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Issue Spec Propose?

Skills that share tags, products or a category with Issue Spec Propose: Geo Proposal (sickn33/agentic-awesome-skills, 47k stars), Continue (telegramdesktop/tdesktop, 33k stars), Better Proposals Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Continuous Learning (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Spec Propose?

higress-group (a GitHub organization) maintains it in higress-group/higress, which has 9,505 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: higress-group/higress on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.