docs: select epic-named projects and link authored tasks - #45
Merged
Merged
Conversation
ark-archastro
force-pushed
the
feat/epic-project-guidance
branch
from
October 2, 2026 04:43
d90b028 to
d6c2384
Compare
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.
Review on ArchCode
Problem and author intent
Agents currently reuse any broad project that covers their work, even when an epic exists. The requested behavior is to reuse or create an active project with the epic's exact name and matching scope, then assign both epic and project to tasks.
What changed
Update ArchDev, monitor, and Tasks guidance to follow that selection rule, resolve duplicate names by scope, and preserve project IDs across name changes. Explain the CLI capability check and reader-first rollout before project names exceed 80 characters.
Scope: documentation only. User impact: newly authored tasks and stream posts share the selected epic-named project. Risk: low; no runtime or ownership changes, but agents must upgrade before using the new task flags.
Testing and rollout
Independent review verified consistent selection rules and compatibility instructions;
git diff --checkpasses. This documentation repository has no executable end-to-end proof for deployed agent behavior. Runtime proofs live in the companion firstlanding implementation; releasing these skills alone does not release those capabilities.Deploy updated CLI readers and the expanded project schema before using names longer than 80 characters. Agents check
tasks create --helpfor--projectand upgrade if absent.Companion runtime implementation: firstlanding #16134.
Conflict resolution: rebased onto current main, preserving upstream installation/reporting consent and organization-stream terminology.
TMPDIR=/private/tmp bash scripts/test-skill-bootstrap.shpasses all 24 cases;.github/workflows/skill-bootstrap-checks.ymlruns this script on PRs. macOS default temporary-path aliases cause an unrelated string-comparison failure, so the local run uses a canonical temporary path. PowerShell checks remain CI-only. Independent review andgit range-diffconfirm no upstream guidance was lost.