Download the PHP package satoved/lararalph without Composer

On this page you can find all versions of the php package satoved/lararalph. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of satoved/lararalph

Informations about the package lararalph

Lararalph

Latest Version on Packagist Total Downloads

Laravel package that wraps the Ralph Wiggum technique into Artisan commands and Laravel-grade UX. Define requirements, plan implementation, build — through a specs-driven workflow with Claude Code doing the work in agentic loops.

What is the Ralph Wiggum Technique?

The Ralph Wiggum technique is a development methodology where Claude runs in an agentic loop: given a prompt, it reads your codebase, reasons about what to do, writes code, runs tests, and iterates until the task is complete. Each iteration gets a fresh context window. The implementation plan file on disk acts as shared state between iterations.

The core idea: three phases, two prompts, one loop.

  1. Define requirements — human + Claude conversation produces specs
  2. Plan — Claude analyzes specs vs existing code (gap analysis), produces a prioritized task list
  3. Build — Claude picks one task per iteration, implements, tests, commits, loop restarts with fresh context

Workflow

Specs Directory

The package manages a specs/ directory in your project root:

Requirements

Installation

Publish config, specs directory, and Claude skill:

Usage

1. Define Requirements

Inside Claude Code, use the /prd skill:

Claude asks clarifying questions about the feature, then writes specs/backlog/2026-01-15-user-notifications/PRD.md. The PRD focuses on what (functional requirements, acceptance criteria, user stories) — no implementation details.

2. Plan

Claude studies your codebase against the PRD using subagents, performs gap analysis, and produces IMPLEMENTATION_PLAN.md — a prioritized bullet-point checklist of tasks to implement.

The plan is disposable. If it's wrong, regenerate it with --force. One planning loop is cheap compared to building from a bad plan.

3. Build

Each loop iteration: Claude reads the plan, picks the most important unchecked task, implements it, runs tests, updates the plan, and commits. Then the loop restarts with a fresh context window and Claude picks the next task.

Worktrees

Use --create-worktree on ralph:plan or ralph:build to run in an isolated git worktree:

This creates a sibling directory (e.g., ../myapp-2026-01-15-user-notifications/), copies .env with adjusted URLs, and runs setup commands (composer install, etc).

Configuration

config/lararalph.php:

Customizing Prompts

Planning and building prompts are Blade templates. Publish them:

Edit resources/views/vendor/lararalph/prompts/plan.blade.php and build.blade.php to adjust how Claude approaches planning and building. This is where you steer Ralph — add guardrails, change subagent counts, adjust backpressure instructions.

Customizing the PRD Skill

Published to .claude/skills/prd/SKILL.md. Edit to match your team's PRD template.

Commands

Command Description
ralph:plan {spec?} Gap analysis: specs vs codebase → IMPLEMENTATION_PLAN.md
ralph:build {spec?} Pick task, implement, test, commit, loop
ralph:finish List and remove git worktrees

Testing

Credits

License

The MIT License (MIT). Please see License File for more information.

All versions of lararalph with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
spatie/laravel-package-tools Version ^1.16
illuminate/contracts Version ^11.0||^12.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package satoved/lararalph contains the following files

Loading the files please wait ...