Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

openspec-propose/explore skill reference specific artifacts

Open Beginner friendly
#2,084 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown, typescript

Research direction

The skill text for openspec-propose and openspec-explore names proposal.md, design.md and tasks.md in its intro and examples; start by locating those skill definitions in the repository. Replace the hardcoded artifact names with wording that refers to the artifacts the active schema produces, keeping the default names only as examples. Done when neither skill tells an agent to expect a fixed artifact set and the default schema still reads correctly.

Written by the indexing model from the issue text.

Description

bug needs-triage
What happened

I have a custom (simpler) schema, with assumes different artifacts as compared to the default ones. The openspec-propose/explore skills, however, reference spec-driven default artifacts (proposal.md, design.md, tasks.md) so their are not compatible with custom schema.

What you expected instead

Openspec procedures should be general enough to work with any schema, and it currently is for the most part. Only the intro text and the examples in the skill name proposal.md, design.md and tasks.md. I have not encountered any failure. The risk is that an agent follows the examples literally and expects artifacts that the custom schema does not produce.

Minimal steps to reproduce

Read skills openspec-propose and openspec-explore

OpenSpec version

1.14.1

Coding agent and model

No response

OS and Node version

No response

Dominant language
TypeScript
Stars
71.6k
Forks
4.9k
Avg merge
1d 20h
Merged PRs (30d)
63

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Fission-AI/OpenSpec

All issues in Fission-AI/OpenSpec

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.