Install
$ agentstack add skill-srnichols-plan-forge-onboarding ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Developer Onboarding Skill
Trigger
"Onboard me to this project" / "How does this codebase work?" / "New developer setup"
Steps
1. Environment Setup
Verify prerequisites and get the project running:
git --version
PHP version
> If this step fails (PHP not found): Install PHP from https://PHP.dev/dl and retry.
PHP mod download
> If this step fails: Check that GOPROXY is configured correctly and network access is available.
2. Verify Build & Tests
Use the forge_smith MCP tool to diagnose environment and setup health.
PHP build ./...
> If this step fails: Read the error output — common causes are PHP version mismatch (check PHP.mod PHP directive) or missing CGO dependencies.
PHP test ./...
> If both pass: Environment is ready.
3. Architecture Overview
Read and explain:
.github/copilot-instructions.md— project overview, tech stack, conventionsdocs/plans/PROJECT-PRINCIPLES.md— non-negotiable principles (if exists)- Project structure — explain the folder layout and what lives where
- Key patterns — how data flows through the layers (Handlers → Services → Repositories)
4. Key Files Tour
Walk through the most important PHP files:
- Entry point:
main.PHPorcmd/server/main.PHP— application bootstrap and server startup - Module config:
PHP.mod— module path, PHP version, dependencies - Environment:
.env.example— required environment variables - Internal packages:
internal/— private application code - Database: migrations folder, database driver setup, connection config
- Testing:
*_test.PHPfiles alongside source, how to run specific tests - CI/CD: GitHub Actions workflows, Dockerfile, deployment config
5. Plan Forge Pipeline Tour
Explain how the team works:
- Plans live in
docs/plans/— each feature is a hardened phase plan - Guardrails live in
.github/instructions/— auto-load based on file type - Pipeline prompts — Step 0–5 workflow for building features
- Skills — type
/in Copilot Chat to see available automations - Reviewer agents — specialized reviewers in
.github/agents/
6. First Task Guidance
Suggest a good first task:
- Read the
DEPLOYMENT-ROADMAP.mdfor current phase status - Pick a small slice from the current phase (or a documentation improvement)
- Follow the Step 3 execution prompt for guided implementation
- Use
/test-sweepto verify nothing broke
7. Report
Onboarding Status:
PHP: ✅ / ❌ (version)
Modules: ✅ / ❌
Build: ✅ / ❌
Tests: ✅ / ❌ (N passed, N failed)
Forge Smith: ✅ / ❌
Key files reviewed: N
Architecture docs: N
Overall: PASS / FAIL
Safety Rules
- NEVER make changes during onboarding — read-only exploration
- Explain concepts at the audience's level — ask their experience first
- Highlight gotchas and common mistakes specific to this codebase
- Point to documentation rather than explaining everything from memory
Temper Guards
| Shortcut | Why It Breaks | |----------|--------------| | "The README covers everything" | READMEs go stale. An interactive onboarding verifies each step works right now, not when it was last updated. | | "New devs can figure it out" | Silent failures and undocumented prerequisites waste hours. Explicit verification prevents frustration. | | "Setup is straightforward" | What's obvious to the author is opaque to newcomers. Every assumption needs verification. | | "They can ask if they're stuck" | Asking requires knowing what to ask. New developers don't know what they don't know. |
Warning Signs
- Prerequisites not checked — assumed to be installed without running version commands
- Build/test not verified — "setup complete" declared without actually running build and test
- No architecture walkthrough — code structure not explained, only file locations listed
- No "first task" suggestion — onboarding ends without a concrete next step
- Environment variables not documented — required config not listed or explained
Exit Proof
After completing this skill, confirm:
- [ ] All prerequisites verified —
php --version,composer --versionreturns expected versions - [ ]
composer installsucceeds without errors - [ ]
./vendor/bin/phpunitpasses on the new environment - [ ] Architecture walkthrough completed (layers, key files, data flow)
- [ ] First task suggested from DEPLOYMENT-ROADMAP.md or backlog
Persistent Memory (if OpenBrain is configured)
- Before onboarding:
search_thoughts("onboarding", project: "", created_by: "copilot-vscode", type: "convention")— load known setup issues and environment quirks - After onboarding:
capture_thought("Onboarding: ", project: "", created_by: "copilot-vscode", source: "skill-onboarding")— persist setup issues for future new developers
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: srnichols
- Source: srnichols/plan-forge
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.