DavidCho1999/archaiflow-skills / bundles/construction-admin/skills/change-order-tracker
change-order-tracker
VerifiedKeeps one dated log of every change from the moment it is first raised, not from the moment it becomes a change order: records where each one came from, what instrument carried it, its cost and time position at every stage, and who it is sitting with, so that the work directed but not yet priced and the changes stalled between proposal and execution are both visible. Reports the running total against the contingency and the count of changes proceeding on direction alone. Trigger on "change order log", "track changes", "how much have we spent of the contingency", "what changes are outstanding", "work proceeding without a change order", "change-order-tracker", or a change register handed over to keep. Carries no cost data, no markup rates and no contract periods; all come from the contract and the proposals. It does not price, review, or negotiate a change — `change-order-review` does that for one — and does not replace the Architect of Record.
Security report
VerifiedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
d291a948cfb23dcc489138f7bbd1fc4efc8509c0- Content hash
8c6a33c4fbedde4c7fbfa29de9f6c296c54d2a4ed0430cedf5ad29a776fedd64- Scanned
- 2026-11-17
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- Every required check completed with no open blocking or medium findings.
- Verification expires
- 2026-12-17
Findings (none)
No findings were recorded.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
Checks skipped
- dependencies: No dependency manifest in the skill directory.
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |