skill ship

Other Community

Skill notes

When to Use

Use this skill when user asks: "Ship the project" or "We're done" "Finalize this" or "Let's deliver" "Complete the project" or "Ready to ship" "Mark as shipped" or "Time to deliver"

Phase 1: Verify Project Ready to Ship

Step 1: Check .octo/ Exists If .octo/ does not exist: STOP. Do not proceed. Step 2: Read STATE.md Status Step 3: Validate Ready State

Phase 2: Multi-AI Security Audit

Step 1: Display Visual Indicators Output: Step 2: Execute orchestrate.sh Security Audit You MUST execute this via native shell command tool:

MANDATORY COMPLIANCE

CRITICAL: You are PROHIBITED from: Skipping Multi-AI validation Doing single-provider analysis instead Claiming you're "simulating" the audit Proceeding without running orchestrate.sh

Phase 3: Capture Lessons Learned

Step 1: Ask User for Lessons Wait for user response. Step 2: Append to LESSONS.md If user provides lessons (not "skip"): Count total lessons:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Verify Project Ready to Ship

Step 1: Check .octo/ Exists If .octo/ does not exist: STOP. Do not proceed. Step 2: Read STATE.md Status Step 3: Validate Ready State

02
Phase 2: Multi-AI Security Audit

Step 1: Display Visual Indicators Output: Step 2: Execute orchestrate.sh Security Audit You MUST execute this via native shell command tool:

03
Phase 3: Capture Lessons Learned

Step 1: Ask User for Lessons Wait for user response. Step 2: Append to LESSONS.md If user provides lessons (not "skip"): Count total lessons:

04
Phase 4: Archive Project State

Step 1: Create Archive Directory Step 2: Copy State Files to Archive IMPORTANT: NEVER archive LESSONS.md - lessons are preserved across projects. Step 3: Verify Archive

05
Phase 5: Create Delivery Summary

Step 1: Update STATE.md Step 2: Create Shipped Checkpoint Step 3: Count Metrics

06
Phase 6: Display Completion

Present final summary:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.