Build a reusable /architecture skill with progressive disclosure #530
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#530
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deferred from hyperthrive-websites #18 on 2026-09-04. Jared has a written design: tiny trigger in CLAUDE.md; per-project docs/architecture/profile.md (30-60 lines); one /architecture skill whose SKILL.md holds the selection procedure (fits an existing seam -> stop; else classify workload and load exactly one references/*.md guide: domain-centered-core, request-response, data-pipeline, workflow-process-manager, event-driven-worker); path-scoped rules in .claude/rules for routine enforcement. First consumer: hyperthrive-astro-scaffold already has profile.md + a path rule + ADR-0001 written by hand, so the skill can be validated against it. Discovered while forking the scaffold; not built because it is not on the cash-flow path.