Hybrid Synchronization
Use When
- synchronising a Water-Scrum-Fall project so Agile backlog items, DoR/DoD, and delivery evidence remain tied to the approved baseline; use requirements-management for baseline change control itself.
- Use this procedure when the required source artefacts are available and
Hybrid synchronisation records is the next lifecycle deliverable.
Do Not Use When
- Use
requirements-management when that neighbouring route owns the decision or deliverable.
- Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.
Required Inputs
| Artefact |
Source or provider |
Required? |
Behaviour when missing |
| Methodology decision, baseline identifiers, backlog, DoR/DoD, and release evidence |
Project context, registries, and delivery owners |
Yes |
Stop the affected step, name the missing source, and return only a qualified gap record. |
Workflow
- Inspect the required inputs and log the exact sources, versions, and unresolved assumptions.
- Apply this skill's existing domain workflow and decision rules to produce
Hybrid synchronisation records.
- Stop when a required source, accountable decision owner, or deterministic test oracle is absent.
- Recover by preserving valid work, marking the blocked scope, and returning the narrowest qualified artefact plus the next evidence needed.
Outputs
| Artefact |
Consumer |
Acceptance condition |
| Hybrid synchronisation records |
Product, requirements, delivery, testing, and governance owners |
Required sections are populated, source links resolve, and every material requirement or decision has an observable review or test oracle. |
Evidence Produced
| Evidence |
Reviewer |
Acceptance condition |
Source, decision, trace, and validation record for Hybrid synchronisation records |
Requirements quality reviewer |
Inputs used, decisions made, checks run, failures, and unassessed items are explicit. |
Capability and permission boundaries
Read and search are required. Editing is allowed only when the request authorises creation or repair of the named requirements artefact. Publishing, production mutation, destructive action, spending, and certification require explicit authority.
Degraded mode
Fallback: if a required file, reviewer, standard source, network check, renderer, or execution capability is unavailable, return the narrowest useful qualified result and mark the affected check not assessed; never convert an unassessed check into a pass.
Decision Rules
| Choice or condition |
Action |
Failure or risk avoided |
| A backlog item changes a baselined requirement without an approved trace or change record |
Block sprint commitment and route the delta through change control. |
Agile delivery drifting from the contractual baseline. |
| Required inputs and test oracles are complete |
Continue through the existing workflow and record evidence. |
A deliverable whose acceptance cannot be reproduced. |
| A mandatory source or owner is missing |
Stop the affected branch and issue a qualified gap record. |
Fabricated context or unauthorised decisions. |
Quality Standards
- Preserve stable identifiers and bidirectional traceability from project evidence to
Hybrid synchronisation records and its acceptance checks.
- Apply ISO/IEEE measures only with a named metric, method, threshold, evidence source, and responsible reviewer; run the anti-slop gate before release.
Anti-Patterns
- Producing
Hybrid synchronisation records from assumed context. Fix: cite the project source or mark the scope blocked.
- Accepting a material requirement without a deterministic oracle. Fix: add a measurable result, boundary, and verification method.
- Crossing into
requirements-management without routing the decision. Fix: hand off the named input and preserve trace links.
- Treating an unavailable check as passed. Fix: mark it
not assessed and state the release consequence.
- Claiming standards, statutory, or stakeholder approval without evidence. Fix: cite the source and reviewer or qualify the claim.
References
When to use
Invoke after Phase 02 Waterfall SRS is signed off and before the team starts sprint planning. Skip if the project is pure Waterfall or pure Agile.
Inputs
Read from projects/<ProjectName>/_context/:
vision.mdfeatures.mdquality-standards.mdmethodology.md (if it exists; otherwise generate from prompts below)
Read from projects/<ProjectName>/02-requirements-engineering/:
- the SRS section files (any
*.md with phase frontmatter 02)
Stimulus / Process / Response
- Read inputs above.
- Extract every baselined
FR- and NFR- from the SRS sections.
- Prompt the consultant for: (a) the change-control body, (b) the cadence (sprint length), (c) which features are baseline-locked vs flexible.
- Render each template with the gathered values:
methodology.md to projects/<ProjectName>/_context/methodology.mdbaseline-trace.yaml to projects/<ProjectName>/_registry/baseline-trace.yamldor-dod.md to projects/<ProjectName>/07-agile-artifacts/definitions/dor-dod.md
- Run
python -m engine validate <project> and report the result.
Output Contract
After running this skill, the kernel's HybridSyncGate MUST pass. If it does not, do not proceed to Phase 07.
1---2name: hybrid-synchronization3description: Use when synchronising a Water-Scrum-Fall project so Agile backlog items, DoR/DoD, and delivery evidence remain tied to the approved baseline; use requirements-management for baseline change control itself.4---56# Hybrid Synchronization78<!-- local-contract-start -->9<!-- dual-compat-start -->10## Use When1112- synchronising a Water-Scrum-Fall project so Agile backlog items, DoR/DoD, and delivery evidence remain tied to the approved baseline; use requirements-management for baseline change control itself.13- Use this procedure when the required source artefacts are available and `Hybrid synchronisation records` is the next lifecycle deliverable.1415## Do Not Use When1617- Use `requirements-management` when that neighbouring route owns the decision or deliverable.18- Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.1920## Required Inputs2122| Artefact | Source or provider | Required? | Behaviour when missing |23| --- | --- | --- | --- |24| Methodology decision, baseline identifiers, backlog, DoR/DoD, and release evidence | Project context, registries, and delivery owners | Yes | Stop the affected step, name the missing source, and return only a qualified gap record. |2526## Workflow27281. Inspect the required inputs and log the exact sources, versions, and unresolved assumptions.292. Apply this skill's existing domain workflow and decision rules to produce `Hybrid synchronisation records`.303. Stop when a required source, accountable decision owner, or deterministic test oracle is absent.314. Recover by preserving valid work, marking the blocked scope, and returning the narrowest qualified artefact plus the next evidence needed.3233## Outputs3435| Artefact | Consumer | Acceptance condition |36| --- | --- | --- |37| Hybrid synchronisation records | Product, requirements, delivery, testing, and governance owners | Required sections are populated, source links resolve, and every material requirement or decision has an observable review or test oracle. |3839## Evidence Produced4041| Evidence | Reviewer | Acceptance condition |42| --- | --- | --- |43| Source, decision, trace, and validation record for `Hybrid synchronisation records` | Requirements quality reviewer | Inputs used, decisions made, checks run, failures, and unassessed items are explicit. |4445## Capability and permission boundaries4647Read and search are required. Editing is allowed only when the request authorises creation or repair of the named requirements artefact. Publishing, production mutation, destructive action, spending, and certification require explicit authority.4849## Degraded mode5051Fallback: if a required file, reviewer, standard source, network check, renderer, or execution capability is unavailable, return the narrowest useful qualified result and mark the affected check `not assessed`; never convert an unassessed check into a pass.5253## Decision Rules5455| Choice or condition | Action | Failure or risk avoided |56| --- | --- | --- |57| A backlog item changes a baselined requirement without an approved trace or change record | Block sprint commitment and route the delta through change control. | Agile delivery drifting from the contractual baseline. |58| Required inputs and test oracles are complete | Continue through the existing workflow and record evidence. | A deliverable whose acceptance cannot be reproduced. |59| A mandatory source or owner is missing | Stop the affected branch and issue a qualified gap record. | Fabricated context or unauthorised decisions. |6061## Quality Standards6263- Preserve stable identifiers and bidirectional traceability from project evidence to `Hybrid synchronisation records` and its acceptance checks.64- Apply ISO/IEEE measures only with a named metric, method, threshold, evidence source, and responsible reviewer; run the anti-slop gate before release.6566## Anti-Patterns6768- Producing `Hybrid synchronisation records` from assumed context. Fix: cite the project source or mark the scope blocked.69- Accepting a material requirement without a deterministic oracle. Fix: add a measurable result, boundary, and verification method.70- Crossing into `requirements-management` without routing the decision. Fix: hand off the named input and preserve trace links.71- Treating an unavailable check as passed. Fix: mark it `not assessed` and state the release consequence.72- Claiming standards, statutory, or stakeholder approval without evidence. Fix: cite the source and reviewer or qualify the claim.7374## References7576- [Skill authoring and release standard](../../../docs/skill-authoring-standard.md)77- [Water Scrum Fall Patterns](references/water-scrum-fall-patterns.md)78<!-- dual-compat-end -->79<!-- local-contract-end -->8081## When to use8283Invoke after Phase 02 Waterfall SRS is signed off and before the team starts sprint planning. Skip if the project is pure Waterfall or pure Agile.8485## Inputs8687Read from `projects/<ProjectName>/_context/`:8889- `vision.md`90- `features.md`91- `quality-standards.md`92- `methodology.md` (if it exists; otherwise generate from prompts below)9394Read from `projects/<ProjectName>/02-requirements-engineering/`:9596- the SRS section files (any `*.md` with phase frontmatter `02`)9798## Stimulus / Process / Response991001. Read inputs above.1012. Extract every baselined `FR-` and `NFR-` from the SRS sections.1023. Prompt the consultant for: (a) the change-control body, (b) the cadence (sprint length), (c) which features are baseline-locked vs flexible.1034. Render each template with the gathered values:104 - `methodology.md` to `projects/<ProjectName>/_context/methodology.md`105 - `baseline-trace.yaml` to `projects/<ProjectName>/_registry/baseline-trace.yaml`106 - `dor-dod.md` to `projects/<ProjectName>/07-agile-artifacts/definitions/dor-dod.md`1075. Run `python -m engine validate <project>` and report the result.108109## Output Contract110111After running this skill, the kernel's `HybridSyncGate` MUST pass. If it does not, do not proceed to Phase 07.
peterbamuhigire