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-go
appdezign/lara-pro-cms-project
claude-code
planning
task-tracking
testing
pint
agent-rules

Implement the open tasks of a plan file in .ai/plans/, ticking them off and recording notes. Use when the user says "plan-go", "continue the plan" or wants to build or resume a planned change.

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

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

Implement the plan: $ARGUMENTS

1. **Pick the plan.** Use the given file. Without one, use the plan in `.ai/plans/` with `Status: in progress`, otherwise the most recent `draft`. If that is ambiguous, list the candidates and ask.
2. **Load context.** Read the whole plan, including Decisions and Notes, and the `.ai/rules` files that cover the paths in its tasks. Set `Status: in progress`.
3. **Work through the open tasks in order.** For each task:
   - Implement it, following CLAUDE.md and the rules.
   - Run the narrowest test that covers it, and Pint on the changed PHP files.
   - Tick it off (`- [x]`) in the plan file right away, so the plan stays accurate if the session ends.
4. **When reality differs from the plan** (a wrong assumption, a missing step, a better approach), stop and tell the user before deviating. Record what changed in Decisions or Notes, and add or adjust tasks.
5. **Finish** with a short report: tasks done, tasks open and anything noted. When all tasks are done, suggest `/plan-check`.

Implement the plan: $ARGUMENTS

  1. Pick the plan. Use the given file. Without one, use the plan in .ai/plans/ with Status: in progress, otherwise the most recent draft. If that is ambiguous, list the candidates and ask.
  2. Load context. Read the whole plan, including Decisions and Notes, and the .ai/rules files that cover the paths in its tasks. Set Status: in progress.
  3. Work through the open tasks in order. For each task:
    • Implement it, following CLAUDE.md and the rules.
    • Run the narrowest test that covers it, and Pint on the changed PHP files.
    • Tick it off (- [x]) in the plan file right away, so the plan stays accurate if the session ends.
  4. When reality differs from the plan (a wrong assumption, a missing step, a better approach), stop and tell the user before deviating. Record what changed in Decisions or Notes, and add or adjust tasks.
  5. Finish with a short report: tasks done, tasks open and anything noted. When all tasks are done, suggest /plan-check.
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.
adachsoft/changelog-linter
adachsoft/collection
payerurl/telegrambot-crypto-payment-instant-payout
dskripchenko/laravel-hybrid-search
riorizkyrainey/lara-ced
mehedimi/static-vel
zharp/zharp
nonsapiens/bigquery-model-sync
lgu-bayambang-ict-office/lgu-laravel-development-standards
andydefer/laravel-support
se7enxweb/flysystem
lampwick/laravel
jeslage/statamic-emojis
micahdshackelford/rmap-laravel
draftsmaninc/draftsman
square-bit/laravel-volition
himito/laravel-mailman
htinlynn/genius-helper
maco-studios/hephaestus
elmogy/larafast