Re-sync agentic workflow guide + add the NetPace "sidekick" delta - #232
Merged
Conversation
- docs/agentic-workflow.md — the generic, stack-portable guide, refreshed to the
current version and kept stack-neutral.
- docs/agentic-workflow-NetPace.md — the NetPace delta ("sidekick"), recording where
NetPace's concrete harness differs from the generic guide: CI + agent-review action
(Review B), the NuGet + cross-platform release pipeline, Change-Intent-Records +
memory as the decision ledger, the enforcement gates (green-gate, no-skipped,
traceability, format-on-commit, PR pre-flight), and console-output snapshot
verification. Flags one unreconciled divergence: format-on-commit vs the guide's
ship-cadence recommendation.
- Delete docs/agentic-software-development-workflow.md — superseded by the two above.
Both docs stand alone: all framing is relative to the generic guide only, with no
reference to any external/sibling repository.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T6dd1XBNhEq42D6EsY6nPz
FrankRay78
force-pushed
the
docs/agentic-workflow-sync
branch
from
July 30, 2026 14:42
6366357 to
0ee45fb
Compare
Three pre-existing references named a private sibling repo — invisible to external readers — in public NetPace files: - .specify/templates/overrides/README.md — "Why <sibling> overrides it" table header, a copy-paste leftover; corrected to "Why this repo overrides it". - docs/change-intent-records/2026-07-10-guard-speckit-files.md — "downstream (<sibling>) trees" reworded to "other repos sharing this harness". - .claude/memory/feedback_read_source_before_designing.md — dropped the sibling-repo origin story; the concrete NetPace incident already carries the lesson. No meaning lost; all framing now stands on its own. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6dd1XBNhEq42D6EsY6nPz
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
NetPace's agentic workflow guide had drifted — an out-of-date copy under a longer filename (
agentic-software-development-workflow.md) — and it lacked a NetPace-specific companion ("delta"/sidekick) doc. This refreshes the generic guide and adds the delta, cleanly splitting the portable principles from NetPace's concrete implementation.What
docs/agentic-workflow.md— the generic, stack-portable guide, refreshed to the current version and kept deliberately stack-neutral.docs/agentic-workflow-NetPace.md— the sidekick. Records only where NetPace's harness differs from the generic guide:claude.ymlmeans the agent review (Review B) posts on the PR.RELEASING.md.Spectre.Console.Testing)./shipcadence or record why it's kept.docs/agentic-software-development-workflow.md— superseded; nothing references it.Both docs are written to stand on their own — all framing is relative to the generic guide, with no reference to any external repository.
Verification
main.Also — repo-wide scrub (2nd commit)
Removed three pre-existing references to a private sibling repo from public files (they leaked a repo external readers can't see, and one was a copy-paste bug):
.specify/templates/overrides/README.md— "Why <sibling> overrides it" → "Why this repo overrides it".docs/change-intent-records/2026-07-10-guard-speckit-files.md— "downstream (<sibling>) trees" → "other repos sharing this harness"..claude/memory/feedback_read_source_before_designing.md— dropped the sibling-repo origin story; the NetPace incident already carries the lesson.A full-repo
git grepnow finds no references to the private repo anywhere in tracked files.