This repository was archived by the owner on Aug 24, 2026. It is now read-only.
AI: Add an Openspec harness for managing updating documentation - #6206
Closed
dfinityianblenke wants to merge 3 commits into
Closed
AI: Add an Openspec harness for managing updating documentation#6206dfinityianblenke wants to merge 3 commits into
dfinityianblenke wants to merge 3 commits into
Conversation
Populate openspec/config.yaml with project context (tech stack, conventions, artifact rules) and create 7 domain-specific specs covering infrastructure, navigation, documentation structure, UI components, search, blog, and deployment. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…NERS Consolidates PR checklist, document tags/SEO requirements, style guide rules, terminology conventions, code snippet formatting, submodule workflow, and CODEOWNERS team assignments into a single OpenSpec specification. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dfinityianblenke
changed the title
raymondk
reviewed
Mar 5, 2026
| @@ -0,0 +1,55 @@ | |||
| # Blog Specification | |||
Contributor
There was a problem hiding this comment.
This is out of date as of yesterday
Contributor
|
@dfinityianblenke since we're repeating this for essentially every agent doesn't it make sense to put all of then in one directory and then symlink it instead? |
Member
|
This repository has been replaced by dfinity/developer-docs, live at docs.internetcomputer.org, and is being archived, so no further merges will happen here. Closing this PR — if the change is still relevant, please open an equivalent PR against dfinity/developer-docs. Thanks for the contribution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add OpenSpec spec-driven development harness to the ICP Developer Portal repository. This provides AI coding assistants (Claude, Gemini, OpenCode) with structured specifications and commands for managing documentation changes through a formal proposal-review-implement workflow.
What's included
openspec/config.yamlplus 8 domain specs backfilled from the existing codebase covering infrastructure, navigation, documentation structure, UI components, search, blog, deployment, and contribution guidelines/opsx new,/opsx apply,/opsx archive, etc.) and skill definitions for Claude Code (.claude/), Gemini (.gemini/), and OpenCode (.opencode/)Why
The portal repo is large and complex. OpenSpec gives AI assistants structured context about the codebase's architecture, conventions, and requirements so they can propose and implement documentation changes more reliably — with formal proposals, validation, and traceability rather than ad-hoc edits.
Notes
.claude/,.gemini/,.opencode/) and theopenspec/directorystyle-guide.md,README.md,CODEOWNERS,sidebars.js,docusaurus.config.js, etc.Outcomes
The following PRs were authored using this branch: