Skip to content

DavidCho1999/archaiflow-skills / bundles/code-life-safety/skills/permit-tracker

permit-tracker

Verified

Keeps one dated log of every approval a project has to obtain, from the agencies you name rather than from an assumed list: what each permit is, which agency issues it, what it depends on, who owns it, what has been submitted and when, every comment received and its response, and every expiry. Reads back what is on the critical path and what is waiting on somebody. Trigger on "permit tracker", "track the approvals", "what permits do we need", "permit log", "who owns this approval", "when does the permit expire", "permit-tracker", or a list of agencies named with a request to keep track of them. Carries no agency lists, no review durations, no fee schedules and no permit types; every one comes from the jurisdiction, because they differ between adjacent municipalities and change without notice. It does not file anything, does not predict a duration, and does not replace the expediter, the code consultant, or the Architect of Record.

Security report

Verified

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
d291a948cfb23dcc489138f7bbd1fc4efc8509c0
Content hash
5c90a3e4f661376e062bb643d4578711ca978d06f837a866de033171f89e2b40
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.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall