Taxonomy¶
Shared tagging vocabularies for library assets. Source of truth:
library/taxonomy/*.yaml — this page is generated at build time.
Delivery phase¶
Tag assets with where they sit in the diagnose → plan → implement loop.
| Phase | Meaning |
|---|---|
diagnose |
Find the constraint. Name what is actually holding the team back. |
plan |
Decide how to mitigate or subordinate the key constraint. |
implement |
Do the work in a systematic way; validate the improvement. |
cross-cutting |
Applies across the loop — hygiene, conventions, enablement. |
Maturity (Radar rings)¶
One vocabulary for skill maturity and Radar rings — no mapping layer.
| Tag | Meaning |
|---|---|
assess |
Planned or unproven. Understand it before relying on it. |
trial |
Proven enough to trial on suitable projects. |
adopt |
The default. Adopt unless you have a specific reason not to. |
avoid |
A practice the library deliberately steers teams away from. |
HoEN needs¶
Every asset is tagged to one or more needs from the Hierarchy of Engineering Needs. Browse the model at engineeringneeds.io.
Level 1¶
| Id | Name |
|---|---|
1-people-purpose |
People & Purpose |
1-tech-capability |
Technical Capability |
1-local-dev |
Local Development & IDE |
1-data-storage |
Data & Storage |
1-logging-monitoring |
Logging & Monitoring |
1-work-backlog |
Work Backlog |
1-version-control |
Version Control |
Level 2¶
| Id | Name |
|---|---|
2-quality-engineering |
Quality Engineering |
2-deployment-solutions |
Deployment Solutions |
2-info-mgmt |
Information Management |
2-standards |
Standards Compliance |
2-continuous-integration |
Continuous Integration |
2-infrastructure-as-code |
Infrastructure as Code |
2-security-controls |
Security Controls |
Level 3¶
| Id | Name |
|---|---|
3-helpers-templates-accelerators |
Templates & Golden Paths |
3-static-analysis |
Static Analysis |
3-service-metrics |
Service Metrics |
3-incident-mgmt |
Incident Management |
Level 4¶
| Id | Name |
|---|---|
4-continuous-deployment |
Continuous Deployment |
4-experimentation |
Experimentation |
Level 5¶
| Id | Name |
|---|---|
5-governance |
Governance & Standardisation |
5-quality-of-service |
Quality of Service |
Effort scales¶
Router for which sizing scale to use by plan lifecycle stage. Detail definitions live in skill references.
wall_clock_tshirt¶
- Labels: Trivial, Small, Medium, Large
- Measures: human team capacity (wall-clock, incl. tests and PR review)
- Official reference:
library/skills/remediation-plan/references/task-sizing.md - Invoke when:
- gap analysis sizing
- remediation or production-readiness planning
- sprint capacity and Jira story creation
- stakeholder timeline estimates (days/weeks per phase)
ai_fibonacci¶
- Labels: 1, 2, 3, 5, 8, 13
- Measures: relative delivery complexity under AI-assisted work
- Official reference:
library/skills/plan-effort-estimate/references/scale.md - Invoke when:
- active WIP plan maintenance
- progress summaries and percent-complete tracking
- migration or modernisation step burn-down
Handoff¶
From wall_clock_tshirt → ai_fibonacci when plan moves from draft remediation to active execution.
Plan status¶
Shared vocabulary across markdown plans and machine-readable effort JSON.
| Key | Markdown | Meaning |
|---|---|---|
not_started |
⬜ Not started | Work has not begun |
in_progress |
🔶 In progress | Actively being worked on (optionally branch name, PR number) |
done |
✅ Complete | Merged and validated (optionally commit SHA, PR number, Jira ticket) |
blocked |
❌ Blocked | Cannot proceed — state the blocker |
cancelled |
🚫 Cancelled | No longer needed — state why (markdown-only; not used in effort JSON) |
Notes
- Decision gates from remediation plans are not statuses — track in a Key Decisions table.
- ai_fibonacci effort JSON uses json values only (see plan-effort-estimate input-format.md).