engine/repl/skills/init/SKILL.md
Initialize a new flowai-workflow project. Analyzes the codebase to detect project settings, asks the user to confirm or adjust, then scaffolds the .flowai-workflow/ directory.
npx skillsauth add korchasa/flowai-workflow flowai-workflow-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scaffold a .flowai-workflow/ directory in the current project with workflow
config, agent definitions, memory files, and HITL scripts. The skill analyzes
the project to pre-fill settings, confirms them with the user, then runs
flowai-workflow init non-interactively.
.flowai-workflow/ already exists, inform the user and STOP. Do not
overwrite without explicit confirmation. If the user confirms re-init,
they must remove the directory manually first.Read manifest files to detect:
deno.json → name, package.json → name,
go.mod → module path basename, Cargo.toml → [package] name,
pyproject.toml → [project] name. Fallback: current directory name.git symbolic-ref refs/remotes/origin/HEAD,
extract branch name after refs/remotes/origin/. Fallback: main.deno.json → tasks.check, package.json →
scripts.check or scripts.test, or by stack: cargo test (Rust),
go test ./... (Go), pytest (Python). If no check task but separate
lint and test tasks exist, combine them: e.g. npm run lint && npm test.Present detected values and ask the user to confirm or edit:
I detected the following project settings:
PROJECT_NAME: <detected>
DEFAULT_BRANCH: <detected>
CHECK_CMD: <detected or empty>
Are these correct? If not, tell me what to change.
Wait for user response. Apply any corrections.
Write a temporary YAML answers file. The template uses two separate
placeholders (TEST_CMD, LINT_CMD) — pass the single CHECK_CMD as both:
cat > /tmp/flowai-init-answers.yaml << 'EOF'
PROJECT_NAME: "<value>"
DEFAULT_BRANCH: "<value>"
TEST_CMD: "<CHECK_CMD value>"
LINT_CMD: "<CHECK_CMD value>"
EOF
flowai-workflow init --answers /tmp/flowai-init-answers.yaml
rm /tmp/flowai-init-answers.yaml
Pass through any user-provided flags (--template, --dry-run,
--allow-dirty).
If init fails due to uncommitted changes, ask the user whether to pass
--allow-dirty or commit first, then retry.
After successful scaffold, tell the user:
.flowai-workflow/agents/agent-*.md and adapt prompts
to your project conventions..flowai-workflow/workflow.yaml for workflow structure.flowai-workflow run to execute the first workflow.sdlc-claude (default) — 6-agent SDLC workflow (PM → Architect →
Tech Lead → Developer/QA loop → Tech Lead Review)development
Supervisor for one flowai-workflow run (Codex). Starts or resumes a single workflow, diagnoses failures from run artifacts, patches root causes, resumes the same run. Run inside an isolated Codex worker subagent spawned by the `supervise`/`orchestrate` skill.
development
Long-cycle flowai-workflow orchestrator (Codex). Reads project orchestration policy, selects the next workflow, and returns a structured supervisor delegation request. Run inside an isolated Codex worker subagent spawned by the `orchestrate` skill.
data-ai
Live flowai-workflow run supervisor. Use only for requests to run, monitor, continue, or resume a current workflow now. Exclude last-night, finished, post-mortem, root-cause-report, and conceptual questions.
data-ai
Scaffold or adapt flowai-workflow DAGs in a project. Use for adding flowai-workflow, adapting an existing .flowai-workflow/<name>, validating workflow.yaml, or wiring agent prompts/scripts.