SIFAP classic orchestration
Run the workshop as four evidence-gated stages while keeping reusable procedures in companion skills.
When to invoke
- "Start the SIFAP archaeology stage."
- "Check whether the team can hand off to architecture."
- "Coordinate the SIFAP build stage."
- "Prepare the final operations and review stage."
Inputs
Use $ARGUMENTS to select one stage. If absent, infer the current stage only from artifacts that exist
in the target repository; otherwise ask the team to choose. Never create a branch or GitHub mutation
solely from an inferred stage.
Stage contract
| Stage |
Lead agent |
Required input |
Primary output |
Exit gate |
| Archaeology |
sifap-classic-archaeologist |
Legacy corpus and scope |
Inventory, dependencies, rule candidates, questions |
Behavior claims cite inspected legacy evidence. |
| Architecture |
sifap-classic-architect |
Approved rule candidates and scope |
REQ-NNN specs, ADRs, modular-monolith plan |
Requirements validate and unresolved meaning is not promoted. |
| Build |
sifap-classic-builder |
Approved requirements, plan, and bounded slice |
Modern code and equivalence tests |
Focused tests and builds pass; drift is classified. |
| Evolution |
sifap-classic-quality, then sifap-classic-operations |
Validated implementation and operational scope |
Verification evidence, hardening, reviewed issues/PRs, IaC evidence, retrospective |
Human approvals and validation evidence are recorded. |
Procedure
- Load
sifap-classic-context and the task-relevant references.
- Inspect the selected stage's required inputs; report missing inputs and stop before side effects.
- Invoke or hand off to the stage agent with objective, scope, evidence paths, decisions, and open
questions. The stage agent loads its named companion skills before acting.
- Keep progress evidence-based; do not satisfy gates with arbitrary counts or generated placeholders.
- Evaluate every exit-gate item and identify blockers, unrun checks, and owner decisions.
- Hand off only the minimum durable context needed by the next stage.
Branch and mutation policy
The workshop may use spec/<NNN>-<feature>, impl/<NNN>-<feature>, infra/<component>,
docs/<topic>, and agent/<issue-NN>. Confirm the target repository's real branch policy before branch
creation. Do not stage, commit, push, open an issue, assign an agent, review a PR, merge, deploy, or run
an infrastructure mutation without the applicable explicit approval.
Handoff contract
## SIFAP stage handoff
**From:** <stage and agent>
**To:** <stage and agent>
**Status:** ready | blocked
### Objective and scope
- <bounded outcome>
### Evidence and decisions
- <path or decision>
### Validation
- <check and actual result>
### Open questions and risks
- <owner, question, impact>
Limits
- This skill coordinates stages; it does not duplicate Natural analysis, requirements, implementation,
testing, security, or infrastructure procedures.
- Persona agents are optional aids. A stage agent remains accountable for the stage output and gate.
- No stage gate may claim success from an unrun check or unavailable artifact.
Output template
## SIFAP workshop status
**Stage:** archaeology | architecture | build | evolution
**Status:** ready | in-progress | blocked | complete
### Inputs
| Artifact | Present | Evidence |
| --- | --- | --- |
### Exit gate
| Criterion | Result | Evidence or blocker |
| --- | --- | --- |
### Handoff
- Next agent: <name or none>
- Context: <paths, decisions, questions>
Quality gate
1---2name: sifap-classic-orchestration-23description: Coordinate the SIFAP modernization workshop through archaeology, architecture, build, and evolution stages with evidence gates, role handoffs, branch intent, and observable completion criteria. Use when starting a stage, checking readiness, or handing work to the next SIFAP stage agent.4---56# SIFAP classic orchestration78Run the workshop as four evidence-gated stages while keeping reusable procedures in companion skills.910## When to invoke1112- "Start the SIFAP archaeology stage."13- "Check whether the team can hand off to architecture."14- "Coordinate the SIFAP build stage."15- "Prepare the final operations and review stage."1617## Inputs1819Use `$ARGUMENTS` to select one stage. If absent, infer the current stage only from artifacts that exist20in the target repository; otherwise ask the team to choose. Never create a branch or GitHub mutation21solely from an inferred stage.2223## Stage contract2425| Stage | Lead agent | Required input | Primary output | Exit gate |26| --- | --- | --- | --- | --- |27| Archaeology | `sifap-classic-archaeologist` | Legacy corpus and scope | Inventory, dependencies, rule candidates, questions | Behavior claims cite inspected legacy evidence. |28| Architecture | `sifap-classic-architect` | Approved rule candidates and scope | `REQ-NNN` specs, ADRs, modular-monolith plan | Requirements validate and unresolved meaning is not promoted. |29| Build | `sifap-classic-builder` | Approved requirements, plan, and bounded slice | Modern code and equivalence tests | Focused tests and builds pass; drift is classified. |30| Evolution | `sifap-classic-quality`, then `sifap-classic-operations` | Validated implementation and operational scope | Verification evidence, hardening, reviewed issues/PRs, IaC evidence, retrospective | Human approvals and validation evidence are recorded. |3132## Procedure33341. Load `sifap-classic-context` and the task-relevant references.352. Inspect the selected stage's required inputs; report missing inputs and stop before side effects.363. Invoke or hand off to the stage agent with objective, scope, evidence paths, decisions, and open37 questions. The stage agent loads its named companion skills before acting.384. Keep progress evidence-based; do not satisfy gates with arbitrary counts or generated placeholders.395. Evaluate every exit-gate item and identify blockers, unrun checks, and owner decisions.406. Hand off only the minimum durable context needed by the next stage.4142## Branch and mutation policy4344The workshop may use `spec/<NNN>-<feature>`, `impl/<NNN>-<feature>`, `infra/<component>`,45`docs/<topic>`, and `agent/<issue-NN>`. Confirm the target repository's real branch policy before branch46creation. Do not stage, commit, push, open an issue, assign an agent, review a PR, merge, deploy, or run47an infrastructure mutation without the applicable explicit approval.4849## Handoff contract5051```markdown52## SIFAP stage handoff5354**From:** <stage and agent>55**To:** <stage and agent>56**Status:** ready | blocked5758### Objective and scope59- <bounded outcome>6061### Evidence and decisions62- <path or decision>6364### Validation65- <check and actual result>6667### Open questions and risks68- <owner, question, impact>69```7071## Limits7273- This skill coordinates stages; it does not duplicate Natural analysis, requirements, implementation,74 testing, security, or infrastructure procedures.75- Persona agents are optional aids. A stage agent remains accountable for the stage output and gate.76- No stage gate may claim success from an unrun check or unavailable artifact.7778## Output template7980```markdown81## SIFAP workshop status8283**Stage:** archaeology | architecture | build | evolution84**Status:** ready | in-progress | blocked | complete8586### Inputs87| Artifact | Present | Evidence |88| --- | --- | --- |8990### Exit gate91| Criterion | Result | Evidence or blocker |92| --- | --- | --- |9394### Handoff95- Next agent: <name or none>96- Context: <paths, decisions, questions>97```9899## Quality gate100101- [ ] The selected stage and bounded outcome are explicit.102- [ ] `sifap-classic-context` was loaded before stage work.103- [ ] Required inputs exist and all behavior claims cite evidence.104- [ ] Exit criteria use actual validation rather than arbitrary output counts.105- [ ] No branch, GitHub, deployment, or infrastructure mutation occurred without approval.106- [ ] The handoff contains objective, scope, evidence, decisions, validation, and open questions.
paulasilvatech