architecture-poc
Use when an architecture hypothesis such as a data model, replication approach or performance claim must be proven with a measured proof of concept
- License 许可
- MIT
- 最近更新
- 2026-10-30
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- architecture-poc
- description
- Use when an architecture hypothesis such as a data model, replication approach or performance claim must be proven with a measured proof of concept
03 SKILL.md 正文
Proof of concept
Check an idea with code and numbers instead of arguing about it.
When
Run a PoC only when the hypothesis can be checked with numbers and the user agreed to check it. Examples: a table layout for a new database against a latency target; a streaming replication tool against a throughput target.
Steps
- Write poc/<slug>/README.md with the hypothesis and success criterion before the first run. Use ../architecture-docs/templates/poc-readme.md.
- Write the PoC code in ~/specs/<project>/architecture/poc/<slug>/: schema, seed data, benchmark, prototype. Keep it small and disposable.
- Run locally only: docker compose or testcontainers.
- When work repository code is needed, use a temporary git worktree and remove it afterwards.
- Never target stage or production without the user's explicit permission in this session.
- Repeat each measurement at least three times; keep raw numbers, not only averages.
- Write poc/<slug>/RESULT.md from templates/poc-result.md with raw numbers and a verdict.
- Link RESULT.md from the ADR that relies on it.
- After the user accepts the result, commit the specs repository.
After the verdict
Never copy PoC code into a product repository; write a candidate card instead. If the result is inconclusive, say which measurement would decide it and ask the user whether to run it.
04 同仓库更多 Skills
verify
Use when a change in __SERVICE__ must be checked before review
work-record
Use when you finished work on a tracker task and it must be recorded in the workspace through a merge request.
task-new
Use to create one story in a stream from the stream profile's story template, link it from its scope screens and open a merge request.
task-decompose
Use to split a stream at the decomposition stage into stories - list scope screens without a story, create the accepted stories and close the stage through a merge request.
task-context
Use to gather the context of a story key or a tracker id - its story, stream stage, scope screens, repositories, decisions, mockups and work records.
repos-sync
Use to update clones of your repositories under repos/ and see their branch, lag and uncommitted changes.