Skip to content

AI: Add an Openspec harness for managing updating documentation#6206

Open
dfinityianblenke wants to merge 3 commits intomasterfrom
ai
Open

AI: Add an Openspec harness for managing updating documentation#6206
dfinityianblenke wants to merge 3 commits intomasterfrom
ai

Conversation

@dfinityianblenke
Copy link
Copy Markdown

@dfinityianblenke dfinityianblenke commented Mar 4, 2026

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 and specifications: openspec/config.yaml plus 8 domain specs backfilled from the existing codebase covering infrastructure, navigation, documentation structure, UI components, search, blog, deployment, and contribution guidelines
  • AI agent commands and skills: Slash commands (/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

  • No runtime code or documentation content is changed
  • All additions are in dotfiles (.claude/, .gemini/, .opencode/) and the openspec/ directory
  • The specs were backfilled from existing sources: style-guide.md, README.md, CODEOWNERS, sidebars.js, docusaurus.config.js, etc.

Outcomes

The following PRs were authored using this branch:

dfinityianblenke and others added 3 commits March 4, 2026 13:29
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 dfinityianblenke requested a review from a team as a code owner March 4, 2026 18:53
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 4, 2026

🤖 Here's your preview: https://y2j3u-vaaaa-aaaam-ahtkq-cai.icp0.io

@dfinityianblenke dfinityianblenke changed the title Ai: Add an Openspec harness for managing updating documentation AI: Add an Openspec harness for managing updating documentation Mar 4, 2026
@@ -0,0 +1,55 @@
# Blog Specification
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is out of date as of yesterday

@raymondk
Copy link
Copy Markdown
Contributor

raymondk commented Mar 5, 2026

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants