project-scaffolding
Skill0 starsChanged 6 months agoMITView on GitHub
Drive Project Scaffolding Track end-to-end. Dispatches project-scaffolder through Intake -> Extract -> Assemble -> Handoff to seed a fresh install from collected docs, briefs, or notes.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir own version, first seen Nov 8, 2026
- cwhited26/pocket-agent-starter-skillstheir own version, first seen Nov 1, 2026
- lubshad/skillstheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- Ghosteken/agent-harnesstheir own version, first seen Oct 1, 2026
Used with
Projects with it also use documentation-site and kubernetes.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
KMaruthi2002Skilldocumentation-site
Plan, build and maintain a documentation website for a product, API, library, platform or internal system: information architecture (tutorials, how-to guides, reference, explanation), choosing a static site generator or hosted docs platform, navigation and search, versioning for multiple releases, generated API reference, code samples that are tested and actually run, docs-as-code workflow with review, previews, link checking and CI, plus accessibility, internationalisation and analytics. Use when someone asks to create a docs site, developer portal, knowledge base, handbook site, migrate docs to a new generator, add versioning or search to docs, or fix docs that users cannot navigate or that have drifted from the product.
Also in 3 projects that use this
mjunaidcaSkillkubernetes
Production-grade Kubernetes manifests and debugging for containerized applications. This skill should be used when users ask to deploy to Kubernetes, create K8s manifests, containerize for K8s, set up Deployments/Services/Jobs/StatefulSets/CronJobs, create namespaces with resource quotas, set up multi-team isolation, configure ResourceQuota/ LimitRange, secure with RBAC (ServiceAccount, Role, RoleBinding), configure init containers (model download, db wait, migrations), set up sidecars (logging, metrics), or debug pods (CrashLoopBackOff, logs, exec, describe, events). Auto-detects from Dockerfile/code, generates hardened manifests with educational comments. CKAD-aligned.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- zeeshanhanif/agentic-sdlc-kit★ 17same name
- fmind/dot★ 13same name
- fmind/dotfiles★ 13same name
- Ghosteken/agent-harness★ 2same name
- third-order-labs/longform-plugin★ 2same name
- hemapriyan-rk/claude-rigor-skills★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
- lubshad/skills★ 1same name
- cwhited26/pocket-agent-starter-skills★ 0same name
- fabioc-aloha/alex-cognitive-architecture★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- plugin-v2/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin-v2/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agents.mdcCursor rule
- agentic-security-reviewSkill
- arc42-baselineSkill
- caveman-commitSkill
- caveman-helpSkill
- caveman-reviewSkill
- cavemanSkill
- create-goalSkill
- design-twiceSkill
- discovery-sprintSkill
- domain-contextSkill
- github-project-setupSkill
- grillSkill
- improve-codebase-architectureSkill
- issue-breakdownSkill
- issue-draftSkill
- issue-pr-syncSkill
- new-adrSkill
- new-glossary-entrySkill
- orchestrateSkill
- portfolio-trackSkill
- product-pageSkill
- project-reviewSkill
- project-runSkill
- quality-assuranceSkill
- quality-metricsSkill
- record-decisionSkill
- review-fixSkill
- roadmap-managementSkill
- sales-cycleSkill
- specorator-designSkill
- specorator-improvementSkill
- specorator-onboardSkill
- stock-takingSkill
- tackle-issueSkill
- tdd-cycleSkill
- token-budget-reviewSkill
- tracer-bulletSkill
- ubiquitous-languageSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Run each phase in order, dispatching the slash command and waiting for the artifact to exist.
- Very specific: line 40
After handoff, recommend the downstream command from recommended_next.
- Distinctive: line 44
Never write to canonical target files directly from this skill.
- Distinctive: line 45
Never turn extracted context into requirements.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Scaffolding
You conduct the Project Scaffolding Track defined in docs/project-scaffolding-track.md. Your job is to sequence phases, gate with the user, and dispatch the project-scaffolder agent. Do not do extraction or starter-pack writing yourself.
Read first
docs/project-scaffolding-track.mddocs/adr/0011-add-project-scaffolding-track.mdmemory/constitution.md- The active
scaffolding/<project>/scaffolding-state.mdif resuming
Flow
| # | Phase | Agent | Slash command | Artifact |
| 0 | Bootstrap | — | /scaffold:start <slug> <source> | scaffolding-state.md |
| 1 | Intake | project-scaffolder | /scaffold:intake | intake.md, source-inventory.md |
| 2 | Extract | project-scaffolder | /scaffold:extract | extraction.md |
| 3 | Assemble | project-scaffolder | /scaffold:assemble | starter-pack.md |
| H | Handoff | project-scaffolder | /scaffold:handoff | handoff.md |
Procedure
- Intake gate. List
inputs/non-recursively before asking for source pointers — work packages dropped there are the default scaffolding source. Surface every item via a singleAskUserQuestion: "I see N items ininputs/. Which are relevant for this scaffold?" If the user picks items ininputs/, those become (or augment) the source pointer at step 2. Never auto-extract archives — extraction is a separate, explicitly approved step. Cite paths intoinputs/fromintake.mdandextraction.md. Full contract:docs/inputs-ingestion.md. Decision: ADR-0017. - Detect resumable engagements under
scaffolding/withstatus: active,paused, orblocked. - For a fresh engagement, clarify in one user gate:
- project slug,
- source pointer(s) — default to items selected from
inputs/at step 0, - desired starter outputs,
- whether the material describes an existing system that may require Stock-taking.
- Run
/scaffold:start <slug> <source-pointer>. - Run each phase in order, dispatching the slash command and waiting for the artifact to exist.
- Between phases, gate with the user: continue, pause, or re-run with feedback.
- After handoff, recommend the downstream command from
recommended_next.
Constraints
- Never write to canonical target files directly from this skill.
- Never turn extracted context into requirements. That is Stage 3 PM work.
- Route to
/stock-taking:startwhen the sources primarily describe an existing system whose behavior is unknown. - Preserve source confidence and ambiguity through the handoff.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.