OpenSpec Community Support: Channels for Help, Discussion, and Contribution

OpenSpec offers multiple community support channels including a Discord server for real-time chat, GitHub Issues for bug reports, community-maintained schema repositories, and direct contribution workflows via pull requests.

OpenSpec is an open-source project developed by Fission-AI that provides standardized workflow specifications. Getting timely help and contributing back to the ecosystem is straightforward through the project's established support infrastructure, which spans live chat platforms, structured issue tracking, and collaborative documentation.

Real-Time Community Support via Discord

The Discord server serves as the primary venue for live community support. According to the README.md, docs/troubleshooting.md, and docs/opsx.md files, users can join the conversation at https://discord.gg/YctCnvvshC to ask questions, troubleshoot problems, and discuss new ideas with maintainers and other users. This channel is specifically recommended in the FAQ (docs/faq.md) as the go-to place for quick help when you need immediate assistance.

# Join the Discord community (macOS/Linux)

open https://discord.gg/YctCnvvshC

# Or copy the URL into your browser: https://discord.gg/YctCnvvshC

Structured Issue Tracking and Discussions on GitHub

For formal support requests and persistent discussions, OpenSpec leverages GitHub's native collaboration tools.

Reporting Bugs and Feature Requests

The repository uses GitHub Issues to track bugs and feature requests. As documented in docs/opsx.md, users encountering problems should raise a bug on GitHub, providing detailed reproduction steps and context. The README.md outlines the contribution workflow, making it clear how to submit improvements.

# Report a bug or request a feature via GitHub CLI

# (replace <title> and <description> with your details)

gh issue create \
  --title "My new feature request" \
  --body "Describe the problem and why this would help."

Long-Form Discussions

Beyond immediate troubleshooting, the project encourages longer-form architectural discussions through GitHub Discussions, linked from various documentation guides. This provides a searchable archive of community knowledge for complex questions that don't fit the bug-report format.

Contributing Code and Documentation

Community members can directly shape the codebase through the Pull Request workflow. The README.md and MAINTAINERS.md files provide clear guidance on how to submit improvements, bug fixes, or new features. The core maintainers listed in MAINTAINERS.md help triage these contributions, ensuring community input reaches the main branch.

# Contribute a fix via Pull Request

git checkout -b fix-typo

# ... edit files ...

git commit -am "Fix typo in docs"
git push origin fix-typo

# Then open a Pull Request on GitHub for review

Community-Maintained Schemas

OpenSpec supports an ecosystem of community schemas—external workflow definitions maintained by contributors in separate repositories. According to docs/customization.md, users can add these schemas to their projects by copying the schema bundle into the openspec/schemas/<schema-name>/ directory.

For example, to add a community schema:

# Clone the community schema repository

git clone https://github.com/JiangWay/openspec-schemas.git

# Copy the specific schema into your OpenSpec installation

cp -r openspec-schemas/superpowers-bridge openspec/schemas/

# Verify the schema works correctly

openspec schema validate superpowers-bridge

These community schemas are listed in the Customization documentation, creating a distributed ecosystem where users share specialized workflow definitions.

Self-Service Documentation and Troubleshooting

The docs/ folder contains comprehensive guides including Getting Started, FAQ, and Troubleshooting documentation. These resources are regularly updated and designed to answer common questions without requiring direct support. When documentation doesn't resolve the issue, these guides consistently point users to the Discord server for escalation.

Summary

• Discord (https://discord.gg/YctCnvvshC) provides real-time chat support for immediate questions and troubleshooting.
• GitHub Issues offer structured bug reporting and feature request workflows, referenced in docs/opsx.md and the README.md.
• Community schemas allow external contributors to publish reusable workflow definitions in openspec/schemas/<schema-name>/ as documented in docs/customization.md.
• Pull Requests enable direct code contributions, with triage support from maintainers listed in MAINTAINERS.md.
• Documentation in the docs/ folder provides self-service answers, with the FAQ specifically directing users to Discord for additional help.

Frequently Asked Questions

How do I get immediate help with OpenSpec?

For immediate assistance, join the Discord server at https://discord.gg/YctCnvvshC. This is the primary live-chat venue highlighted in the README.md, docs/faq.md, and docs/troubleshooting.md files. The community and maintainers actively monitor this channel for quick questions and troubleshooting scenarios.

Where can I report bugs or request new features?

Submit bug reports and feature requests through GitHub Issues. The docs/opsx.md file explicitly invites users to raise bugs on GitHub, while the README.md explains the contribution workflow. Use the GitHub CLI or web interface to create issues with descriptive titles and detailed reproduction steps.

Can I contribute my own workflow schemas to OpenSpec?

Yes, through community schemas. You can maintain your own schema repository and share it with others. Users can add your schemas to their projects by copying the bundle into openspec/schemas/<schema-name>/, as detailed in docs/customization.md. This distributed approach allows the ecosystem to grow without requiring every schema to be merged into the core repository.

Who maintains the OpenSpec project?

The project is maintained by the core team listed in MAINTAINERS.md, who triage community contributions, review pull requests, and oversee the roadmap. These maintainers work alongside the broader community to ensure the project evolves according to user needs and technical standards.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}