Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
plan-check
appdezign/lara-pro-cms-project
claude-code
plans
verification
code-review
pint
schema-changes
project-constraints

Verify that a plan in .ai/plans/ is fully and correctly implemented. Runs its Verify section and checks every task and decision against the code. Use when the user says "plan-check", "verify the plan" or a planned change is finished.

Install
php artisan boost:add-skill appdezign/lara-pro-cms-project

Save this content to: .claude/skills/plan-check/SKILL.md

Check the plan: $ARGUMENTS

1. **Pick the plan.** Use the given file, otherwise the plan in `.ai/plans/` with `Status: in progress`. If that is ambiguous, ask.
2. **Run the Verify section.** Run every command it lists and report the results faithfully, including failures.
3. **Check against the code.** For each ticked task, confirm that the code actually does it. For each decision, confirm that the implementation follows it. Also check the project constraints in CLAUDE.md that apply (schema changes through the `build*` methods, `_q()` keys, no `RefreshDatabase`, Pint).
4. **Report** in three groups: ✅ done and verified, ⚠️ done but deviating or untested, ❌ missing or failing, each with a `path:line` reference. Do not fix anything in this step; offer to fix the items in ⚠️ and ❌.
5. **Close.** When everything passes, set `Status: done` and suggest running `/code-review` before committing.

Check the plan: $ARGUMENTS

  1. Pick the plan. Use the given file, otherwise the plan in .ai/plans/ with Status: in progress. If that is ambiguous, ask.
  2. Run the Verify section. Run every command it lists and report the results faithfully, including failures.
  3. Check against the code. For each ticked task, confirm that the code actually does it. For each decision, confirm that the implementation follows it. Also check the project constraints in CLAUDE.md that apply (schema changes through the build* methods, _q() keys, no RefreshDatabase, Pint).
  4. Report in three groups: ✅ done and verified, ⚠️ done but deviating or untested, ❌ missing or failing, each with a path:line reference. Do not fix anything in this step; offer to fix the items in ⚠️ and ❌.
  5. Close. When everything passes, set Status: done and suggest running /code-review before committing.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle
glavweb/extra-bundle
glavweb/api-bundle
glavweb/admin-bundle