Files
movq 594fccc80a feat(composer): discovery-phase plugin from "I want an app that..." to tracker-loaded stories
Plugin pairs with Symphony — Composer's output (issues in the project's
tracker) is Symphony's input. State-aware /composer command walks the
user through 11 phases: concept, users (with workflow probing for hidden
actors), requirements/NFR/IA, design system, interaction design, flows,
mocks, architecture, stories, roadmap, load. Each phase produces a
reviewable artifact in docs/planning/ (or, for design and interaction,
a project-local skill — see below).

Architecture is intentionally LAST, after the spec is complete. Mocks
are JSX/TSX regardless of final stack and pass a "text feasibility"
audit — every visible string is categorized (static/computed/authored),
computed strings are traced to source data, and any string implying an
unspecified feature halts the commit.

Design system and interaction design are produced as PROJECT-LOCAL
SKILLS in .claude/skills/<slug>-design-system/ and
.claude/skills/<slug>-interaction-design/, not as docs in
docs/planning/. Skills auto-load via description matching whenever UI
work happens; a reference doc gets read once and drifts out of context.
The mocks skill imports tokens directly from the design-system skill
for a single source of truth across mocks and (eventually) real code.

ui-system is currently a PLACEHOLDER — captures the minimum needed for
mocks to proceed with <TBD: ...> markers as a return-pass worklist.
Full interview specification is the next pass.

Council touchpoints baked in: PM/skeptic/end-user after requirements,
end-user/a11y after mocks, full architecture council after architecture,
plus auto-additions (legal-triage on regulated data, privacy-advocate
on PII, finance-controller on money flows).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-29 21:03:40 -05:00

50 lines
1.0 KiB
Markdown

# Non-functional requirements
<!--
Every entry needs a NUMBER or NAMED THRESHOLD. "Fast" is not an NFR;
"p95 interaction < 100ms on mid-tier mobile" is.
-->
## Performance
- <metric>: <threshold> at <load>
- <metric>: <threshold> at <load>
## Scale
- Users: <expected at launch> → <year-1 target>
- Data: <volume> at <year-1 target>
- Throughput: <req/s, events/s, etc.>
## Availability
- Target uptime: <%>
- RTO / RPO: <values, if applicable>
## Security
- Authentication: <method>
- Authorization model: <roles / capabilities / none>
- Sensitive data: <classifications>
- Compliance frameworks in scope: <SOC2 / GDPR / HIPAA / none / TBD>
## Accessibility
- Standard: WCAG 2.2 AA (floor — see interaction-design.md for specifics)
## Browser / device support
- <list>
## Offline behavior
- <does the app function offline? what does it do when it can't reach the network?>
## Data retention & deletion
- <policy: how long, who can delete, what's the cascade>
## Observability
- <what we log / measure / alert on, at the requirement level>