Project documentation pack
Reusable file-first kit for AI-assisted landscape design projects.
npx -y skills add charmonye/landkit --skill project-documentation-packAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use after client approval to prepare, audit, or assemble the landscape project documentation set according to the studio's agreed scope for this client.
SKILL.md
1.2 KB, as published. Nobody here has run it
Project Documentation Pack
Goal
Assemble working documentation that matches the approved direction and agreed service scope.
Process
- Check
05_client_approval/APPROVAL_DECISION.md. - Identify the agreed service scope and what is explicitly outside scope.
- Use
06_design_documentation/DOCUMENTATION_CHECKLIST.mdas scope control. - For each sheet, verify connection to measured/CAD plan, not just AI visual.
- Record disputed or temporary decisions in
00_project_admin/DECISIONS.md. - Before delivery, check consistency of plans: zones, dimensions, materials, planting, lighting.
Rules
- AI visual is not a source of dimensions.
- Every drawing must have a clear purpose.
- Do not invent default project variants or package contents.
- If a section is not included in the agreed scope, mark this explicitly instead of leaving it empty without explanation.
Output
- Updated documentation checklist.
- List of completed sheets.
- List of mismatches or missing data.