SeviaFlow Skills

These installable skills give an AI assistant a repeatable SeviaFlow workflow. They are plain SKILL.md files, based on the open Agent Skills format, with instructions focused on Laravel and SeviaFlow applications.

The skill set

Skill	Use it for	Result
Download · `seviaflow-app-discovery`	Starting from an idea or incomplete brief.	A guided interview and a clear application brief with users, scenarios, data, access rules, MVP, assumptions, and acceptance criteria.
Download · `seviaflow-app-planner`	Turning an agreed brief into an implementation plan.	A version-aware map of package choices, Resources, built-in features, Laravel responsibilities, security, tests, stages, and gaps.
Download · `seviaflow-resource-builder`	Implementing a reviewed stage in a Laravel project.	Changes that follow the repository's patterns and the exact installed SeviaFlow APIs, with relevant tests.
Download · `seviaflow-resource-reviewer`	Checking a diff or existing application.	Prioritized findings about defects, authorization, data isolation, test gaps, and relevant SeviaFlow capabilities.

Install in Claude Code

From the root of the Laravel application, run this once. It installs the skills for this project and keeps them available to the team when the .claude/skills directory is committed:

for skill in seviaflow-app-discovery seviaflow-app-planner seviaflow-resource-builder seviaflow-resource-reviewer; do
  mkdir -p ".claude/skills/$skill"
  curl -fsSL "https://seviaflow.io/skills/$skill/SKILL.md" \
    -o ".claude/skills/$skill/SKILL.md"
done

Claude Code discovers project skills from .claude/skills/<skill-name>/SKILL.md. Restart or reopen the session if the skills are not visible. You can invoke one by name or let Claude Code select it when relevant.

Install in OpenAI Codex

From the root of the Laravel repository, run this once. It downloads the same skills into Codex's repository-level skill directory. Commit .agents/skills if you want everyone working in the repository to have them:

for skill in seviaflow-app-discovery seviaflow-app-planner seviaflow-resource-builder seviaflow-resource-reviewer; do
  mkdir -p ".agents/skills/$skill"
  curl -fsSL "https://seviaflow.io/skills/$skill/SKILL.md" \
    -o ".agents/skills/$skill/SKILL.md"
done

Codex scans .agents/skills in the current directory and its parent directories up to the repository root. It usually detects skill changes automatically; restart Codex if a new or updated skill does not appear.

Use the skills in Codex

In Codex CLI or the IDE extension, enter /skills to browse available skills, or mention a skill in your prompt with $. For a new application, start with discovery:

$seviaflow-app-discovery I want to build an app for managing equipment rentals. Help me work out who will use it and what the first version needs.

Once you have a brief, continue through planning, implementation, and review. Approve each implementation stage before moving on:

$seviaflow-app-planner Map the agreed brief to our installed SeviaFlow version and propose small implementation stages.

$seviaflow-resource-builder Implement the first approved stage in this repository. Inspect the installed APIs and existing conventions first.

$seviaflow-resource-reviewer Review the current diff for missing SeviaFlow features, authorization gaps, tenant isolation, and tests.

Try the guided workflow in Claude Code

Start broad and let the discovery skill ask follow-up questions one topic at a time:

/seviaflow-app-discovery I want to build an app for managing equipment rentals. Help me work out who will use it and what the first version needs.

When the brief is ready, move through planning, implementation, and review:

/seviaflow-app-planner Map the agreed brief to our installed SeviaFlow version and propose small implementation stages.

/seviaflow-resource-builder Implement the first approved stage in this repository. Inspect the installed APIs and existing conventions first.

/seviaflow-resource-reviewer Review the current diff for missing SeviaFlow features, authorization gaps, tenant isolation, and tests.

What the skills require from an assistant

Read the existing conversation, repository guidance, Composer version, package configuration, source, examples, and tests before assuming how an API works.
Ask focused questions when an answer changes the data model, user access, workflow, or scope. Explain terms for a beginner and do not repeat questions already answered.
Distinguish native SeviaFlow behavior from Laravel application code and custom extensions.
Prefer existing framework features when they fit, but do not add features just because SeviaFlow supports them.
Never invent a class, method, Artisan command, route, config key, or security default. Mark unknowns and verify them.
Keep authorization explicit. UI panel entry, Laravel policies, optional role permissions, API authentication, and tenant scoping are separate checks.
Make implementation incremental and test each stage. Report assumptions, tests, failures, and remaining gaps.

The skills work as a set or individually. Other tools that support Agent Skills can use the same SKILL.md instructions from their documented skills directory.

See AI-Friendly Development for the overall workflow, the official Claude Code skills guide for Claude Code's project-skill behavior, and OpenAI's Codex skills guide for Codex discovery and invocation. The Agent Skills format is documented at agentskills.io/specification.