feat(workflows): add issue plan automation

.github/workflows/doc-sync.yml

@@ -12,5 +12,5 @@ jobs:
     if: >
       github.event_name == 'workflow_dispatch' ||
       (github.event_name == 'pull_request' && github.actor == github.repository_owner)
-    uses: activadee/codex-shared-workflows/.github/workflows/codex-doc-sync.yml@main
+    uses: activadee/codex-shared-workflows/.github/workflows/doc-sync.yml@main
     secrets: inherit

.github/workflows/issue-plan.yml

@@ -0,0 +1,21 @@
+name: Codex Issue Implementation Plan
+
+on:
+  issues:
+    types:
+      - labeled
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  issue-plan:
+    if: >
+      github.event.action == 'labeled' &&
+      github.event.label.name == 'codex-plan' &&
+      github.actor == github.repository_owner
+    uses: activadee/codex-shared-workflows/.github/workflows/issue-plan.yml@main
+    secrets: inherit
+    with:
+      issue_number: ${{ github.event.issue.number }}

CONTRIBUTING.md

@@ -16,6 +16,10 @@ Thanks for your interest in improving the Codex Go SDK! We welcome issues and pu
 - Keep commits focused; rebase onto the latest `main` when possible
 - Our CI runs `go test ./...` on pushes and pull requests—make sure it passes
 
+## Issue planning automation
+
+Repository maintainers can label an issue with `codex-plan` to trigger the Codex Issue Implementation Plan workflow. The workflow files the implementation outline back on the issue so everyone can see the proposed steps before coding starts.
+
 ## Code of conduct
 
 Be respectful and constructive. We follow the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).