メニュー
Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-operational-sop |
| description | Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
When to use:
User input: A project ID and optionally an SOP type (development-workflow, deployment-guide, all, audit).
Examples:
arkd — Audit and generate all missing SOPswallet development-workflow — Generate development workflow onlyfulmine audit — Only audit, don't generateThis skill generates validated operational documentation by actually testing commands before documenting them.
${ARKADIAN_DIR}/docs/INDEX.md and find project entrydocs_path and repo_path| Type | Indicators | Common Commands |
|---|---|---|
| Go Backend | go.mod, Makefile | make build, make test, go run |
| TypeScript Frontend | package.json + React/Vite | pnpm install, pnpm run start |
| TypeScript Backend | package.json + Node.js | pnpm install, pnpm run dev |
| Infrastructure | *.tf files | tofu init, tofu plan |
| Telemetry | docker-compose.yml + Prometheus | docker compose up |
Check required files:
sop/development-workflow.md # REQUIRED
testing/usage.md # REQUIRED
testing/how_to_run.md # REQUIRED
testing/how_to_test.md # REQUIRED
testing/troubleshooting.md # REQUIRED
Optional (by type): sop/deployment-guide.md, testing/api-reference.md
Report audit results. If audit mode, stop here.
For each missing file, follow the validation-first approach:
sop/development-workflow.md: Prerequisites, Setup, Building, Running, Testing, Quality Checks, PR Checklist
testing/how_to_run.md: Prerequisites, Quick Start, Docker Deployment, Local Development, Configuration, Verification
testing/how_to_test.md: Unit Tests, Integration Tests, Running Specific Tests, Test Coverage, CI/CD
testing/troubleshooting.md: Common Issues (Build Failures, Runtime Errors, Test Failures), Debugging (Logs, Docker Logs, Environment)
## Generation Report for <project-id>
### Commands Validated:
- `make build` - SUCCESS
- `make test` - SUCCESS (23 tests passed)
### Commands Not Validated (require manual verification):
- `make integrationtest` - Requires external dependencies
Analyze a project repository and add it to the Arkadian documentation registry with standardized structure. Use when: user provides a path to a new project to onboard.
Analyse an Arkadian orchestrator session - read transcripts, logs, and artifacts to understand what happened and suggest improvements. Use when: user wants to debug or review a past session.
Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project.
Update project documentation based on new commits and changes in the repository. Use when: user wants to sync docs after project changes.
Self-improvement loop for arkadian. Launches arkadian -d with a GitHub issue, polls until done, evaluates per-agent criteria, reads transcripts on failure, improves prompts, deletes worktree, and relaunches. Loops until passing or max iterations.
Debug and investigate fulmine production issues. Downloads logs and SQLite datadir from remote Docker containers, and queries the Boltz PostgreSQL database remotely. Analyzes errors and queries databases for root cause analysis. Use when: (1) investigating fulmine production errors or failures, (2) checking swap/vHTLC/delegate task status in prod, (3) analyzing fulmine logs for recent issues, (4) debugging VTXO or transaction problems on mainnet, (5) inspecting Boltz swap state in PostgreSQL. Triggers on: "fulmine prod", "production logs", "prod errors", "check prod fulmine", "debug fulmine", "fulmine mainnet issue", "boltz db", "boltz prod".