Echo-aloha/asphalt-codex-skills-5 / skills/pfc5-asphalt-workflow
pfc5-asphalt-workflow
VerifiedOrchestrate PFC2D/PFC3D 5.0 asphalt-mixture case handoff, specimen generation, fistPkg26 integration, Burger calibration, Marshall or rutting tests, validation, and reproducible delivery; use whenever a user mentions PFC5 asphalt, AC mixtures, fistPkg, Marshall, wheel tracking, or rutting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| agents/openai.yaml | config | 327 B |
| dependencies.json | config | 1.4 KB |
| references/fistpkg-contract.md | markdown | 2.6 KB |
| references/intersection-rutting-research-evidence.md | markdown | 5.8 KB |
| references/runtime-verification-manifest.json | config | 2.3 KB |
| references/standards-method-map.md | markdown | 5.9 KB |
| references/standards-policy.md | markdown | 3.2 KB |
| references/standards-source-ledger.json | config | 7.9 KB |
| references/version-matrix.md | markdown | 1.0 KB |
| scripts/check_fistpkg.py | script | 685 B |
| scripts/check_runtime_manifest.py | script | 2.3 KB |
| templates/pfc5-asphalt-intake.yaml | config | 3.5 KB |
| tests/test_check_fistpkg.py | script | 2.1 KB |
| tests/test_pfc5_runtime_assets.py | script | 2.4 KB |
references/standards-policy.md
View on GitHub# Asphalt test standards policy
## Current versus legacy
China's Ministry of Transport announced JTG 3410-2025 with an effective date of
2025-10-01 and simultaneous withdrawal of JTG E20-2011. Therefore:
- default new work to JTG 3410-2025;
- use JTG E20-2011/T0709/T0719 only when reproducing legacy data or when the user
explicitly requires that edition;
- do not assume that method identifiers, dimensions, conditioning, speed, cycle count,
calculation constants or acceptance criteria stayed unchanged;
- record the exact edition, method ID, clause/table and any machine/specimen correction
coefficients in the case manifest.
Official announcements:
- [JTG 3410-2025 release](https://xxgk.mot.gov.cn/jigou/glj/202508/t20250822_4175218.html)
- [JTG E20-2011 legacy release](https://xxgk.mot.gov.cn/jigou/glj/202006/t20200623_3312352.html)
## Modeling rule
A DEM model may simplify geometry or loading, but the result must distinguish:
1. normative test value;
2. physical laboratory input;
3. DEM-equivalent input;
4. numerical control parameter.
Never label an equivalent patch load, accelerated cycle, scaled particle size or
post-peak stop factor as a standard requirement.
## Standard roles and method chains
Do not treat every document containing an asphalt requirement as a laboratory test
method. Classify each source before extracting values:
- JTG 3410-2025 owns asphalt and asphalt-mixture laboratory methods;
- JTG 3432-2024 owns aggregate and filler test methods used to establish measured input;
- JTG D50-2017 supplies pavement-design context and target parameters;
- JTG 3450-2019 supplies field-test definitions for independent validation;
- construction, quality-evaluation and maintenance standards supply project/acceptance
context, not automatic contact parameters;
- subgrade design/construction standards matter only when the model scope includes the
support structure or coupled pavement response.
Freeze a method chain rather than a single method ID: aggregate characterization,
mixture sampling/preparation, specimen forming, density/void measurement, performance
test, field validation and acceptance decision. See
[standards-method-map.md](standards-method-map.md).
Bind every reviewed package-level method claim to
[standards-source-ledger.json](standards-source-ledger.json). Project intake records may
reuse a ledger source ID and digest, but each method-chain item still owns its method,
locator, reviewer, values and model mapping. A digest identifies the reviewed copy; it
does not replace human confirmation of applicability or interpretation.
## Acceptance rule
The skill may compute a metric only after its formula, sampling interval, units and
correction factors are tied to the chosen standard edition. If the current standard text
is unavailable, return the raw force/displacement or rut-depth history and mark the
normative metric as pending rather than filling a remembered value.
Keep raw observations, corrected observations and the final normative metric in separate
columns. Record the person/date of source review and distinguish a printed-page locator
from the PDF viewer page number. Do not bundle the standard PDF or reproduce complete
tables in a public case.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |