feat(unic-ticket-specification): add portable ticket-specification workflow plugin#257
Open
PetersSourceCode wants to merge 2 commits into
Open
feat(unic-ticket-specification): add portable ticket-specification workflow plugin#257PetersSourceCode wants to merge 2 commits into
PetersSourceCode wants to merge 2 commits into
Conversation
…rkflow plugin Package a tracker-agnostic Archon workflow that takes a ticket from intake to "ready for implementation": detect input -> analyze across configured repos + linked docs -> classify Bug vs CR/Story -> rewrite to template -> non-blocking completeness check -> PERT estimate -> human approval gate -> apply (create or update) -> report. All tracker/tenant/repo/OS variability lives in a per-project config; nothing tracker-specific is in the workflow or command templates. - 11-node workflow DAG + 7 uts-* command templates + tracker MCP config + config template - /unic-ticket-specification:setup zero-config slash command (no JS lib) - four plugin ADRs under docs/adr/ - registered in the root marketplace; indexed in AGENTS.md + CONTEXT-MAP.md - Feature record at docs/issues/unic-ticket-specification/PRD.md - example wording in uts-rewrite-crstory genericised (no client-specific names) Refs #256 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
|
Added a generic comment to the referenced issue: #256 (comment) |
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
2 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.
What
Adds
unic-ticket-specification— a Claude Code plugin packaging a portable Archon workflow that takes a tracker ticket from intake to "ready for implementation". Tracker-agnostic (Jira / Azure DevOps / GitHub), multi-repo, and OS-independent (Windows / macOS).Tracking issue: #256 · Feature PRD:
docs/issues/unic-ticket-specification/PRD.mdWorkflow
11-node DAG:
detect-input → analyze → classify → rewrite (Bug | CR-Story) → assess-completeness (non-blocking) → estimate (PERT) → persist-local → present-draft → approval-gate ✓ → apply (create | update) → report. Nothing is written to the tracker before the human approval gate.Contents
.archon/): workflow DAG, sevenuts-*command templates, tracker MCP config, documentedticket-spec.config.example.yaml, bundle README/unic-ticket-specification:setup: zero-config conversational install/config command (ships no JS).claude-plugin/manifests,package.json,CONTEXT.md,AGENTS.md,CLAUDE.mdsymlink,README.md,CHANGELOG.mddocs/adr/): tool-agnostic config-driven, MCP-first/CLI-fallback, Markdown-only descriptions, setup-as-conversational-commandAGENTS.md+CONTEXT-MAP.md(app:unic-ticket-specification)Design notes
ticket-spec.config.yamlis created per project.uts-rewrite-crstory.mdwas genericised (no client-specific names).LICENSEfile added (maintainer manages those by hand per monorepo convention).Validation
pnpm --filter unic-ticket-specification verify:changelogpassestest/typecheckscriptNotes for reviewer
test-git-push-permissionscommit (just the rootAGENTS.mdworkspace-tree line) — squashing on merge will fold it away.pnpm-lock.yamlchange is the new workspace member only.resolved; close it when this merges (Gitflow default branch ismain, so it won't auto-close on the develop merge).🤖 Generated with Claude Code