Skip to content
TrustedSkillsbeta
Back to all skills

Laravel:Writing Plans

Checked
jpcaparas·vlatest·backend·MIT

Generates Laravel project plans, including database schemas, routes, controllers, and basic scaffolding from user requirements.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jpcaparas/superpowers-laravel --skill laravel:writing-plans -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jpcaparas

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jpcaparas/superpowers-laravel at c5198b16cd.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c5198b16cd
Manifest
skills/writing-plans/SKILL.md
Scanned
1 file, 42 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to generate structured development plans specifically tailored for Laravel projects. It analyzes project requirements to outline a step-by-step roadmap, ensuring architectural decisions align with the framework's ecosystem and best practices.

When to use it

  • Initiating new Laravel applications to define feature sets and database schemas before coding begins.
  • Breaking down complex refactoring tasks into manageable migration steps for existing codebases.
  • Planning integration of third-party packages like Sanctum, Horizon, or Telescope into the project lifecycle.
  • Creating a timeline for deploying specific modules in a microservices architecture using Laravel Octane.

Key capabilities

  • Generates comprehensive development roadmaps based on high-level project descriptions.
  • Structures plans to adhere to Laravel-specific conventions and directory organization.
  • Identifies necessary dependencies and package integrations required for the proposed features.
  • Outlines sequential execution steps to minimize conflicts during implementation.

Example prompts

  • "Create a development plan for a new Laravel 11 e-commerce dashboard with Stripe integration and real-time inventory updates."
  • "Outline a migration strategy to move our legacy PHP monolith into a modular Laravel structure using the Octane server."
  • "Draft a step-by-step implementation guide for adding multi-tenant support to an existing SaaS application built with Laravel Forge."

Tips & gotchas

Ensure you provide sufficient context about your current stack (e.g., specific Laravel version, database type) to get a relevant plan. While the skill outlines the strategy, it does not automatically execute the code or configure server environments; manual verification of generated steps is recommended before implementation.