skill factory

Engineering Community

Skill notes

STEP 1: Clarifying Questions (MANDATORY)

Ask via AskUserQuestion BEFORE any other action: Spec location — path to NLSpec file, or paste inline Satisfaction target override (Use spec default / Custom 0.80-0.99) Cost approval — ~$0.50-2.00 for ~20-30 agent calls (Approve / Approve --ci / Decline) If spec path provided inline with the command, use it but still ask remaining questions.

STEP 2: Display Visual Indicators (MANDATORY — BLOCKING)

Check providers: Display banner: Validation: BOTH external providers unavailable → continue with Claude-only (warn user about reduced diversity). At least one available → proceed normally.

STEP 3: Validate Spec File (MANDATORY — Validation Gate)

If spec file missing → STOP, ask user for correct path. If spec is thin (< 50 words) → WARN but proceed. DO NOT proceed past this gate if file does not exist.

STEP 4: Read Prior State (OPTIONAL)

Failure → continue without state, warn user.

Before committing to the expensive embrace phase (~$0.50-2.00), verify that generated scenarios actually cover the spec's edge cases. A quick cross-provider challenge here can prevent wasting an entire factory run on incomplete scenario coverage. After orchestrate.sh parses the spec (Phase 1-2) and before embrace execution (Phase 4), dispatch a scenario coverage review: If a second provider is available (Codex or Gemini), dispatch the challenge:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
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.

Output preview skill-factory.preview
# STEP 7: Read Scores and Present Results (MANDATORY)

SCORES_FILE=$(find .octo/factory -name "satisfaction-scores.json" -mmin -60 2>/dev/null | sort -r | head -1)
if [[ -n "$SCORES_FILE" ]]; then
    cat "$SCORES_FILE"
fi

Discussion

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