mcpField
I
init-project-jpkb

init-project-jpkb

github.com/product-on-purposeProductivity76960 installsUpdated 4d ago
Repository

About init-project-jpkb

init-project-jpkb is a workflow skill for creating projects in the JPKB repository with standardized documentation and directory structures. It gathers project details, preserves existing files, and supports layouts for general, Python, Node.js, 3D-printing, and research projects.

Key features

  1. 01Gather project and category details
  2. 02Confirm the target path
  3. 03Preserve or merge existing files
  4. 04Generate files from templates
  5. 05Five project type layouts

Use cases

  1. 01Creating a documented project in JPKB
  2. 02Scaffolding a research or 3D-printing project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/product-on-purpose/pm-skills --skill init-project-jpkb

After installing, type/init-project-jpkbin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
CHANGELOG.template.md
CONTEXT.template.md
DECISIONS.template.md
LICENSE-Apache2.txt
LICENSE-MIT.txt
README.template.md
TODO.template.md
gitignore-general.txt
references/
project-types.md

Details

From the project README

JPKB Project Initialization Workflow

Scaffold new projects in the JPKB repository with standardized documentation artifacts.

Execution Steps

1. Gather Requirements

Before creating any files, clarify with user:

RequiredQuestionDefault
✓Project name?None — must ask
✓Category/parent folder?Prompt with existing options
Project type?general
License preference?MIT
Brief description?"A new project"

Skip questions if context provides answers. If user says "init parametric-hinge in 3d-prints", don't re-ask.

2. Confirm Target Path

Before creating files, confirm the full path:

Target: E:\Projects\JP KB\jpkb\projects\<category>\<project-name>\

Wait for user confirmation or correction.

3. Check for Existing Files

Before creating, check what already exists:

If ExistsAction
README.mdSkip — preserve existing
CHANGELOG.mdSkip — preserve existing
LICENSESkip — preserve existing
.gitignoreMerge — append missing entries
_NOTES/Skip — preserve existing
AGENTS/Create missing parts only

This allows safe re-runs on existing projects to add agentic structure.

4. Create Directory Structure
<project-name>/
├── README.md
├── CHANGELOG.md
├── LICENSE
├── .gitignore
├── _NOTES/
│   └── .gitkeep
└── AGENTS/
    └── claude/
        ├── CONTEXT.md
        ├── TODO.md
        ├── DECISIONS.md
        └── SESSION-LOG/
5. Populate Files

Use templates from assets/ folder, substituting:

  • {{PROJECT_NAME}} — Project name
  • {{DESCRIPTION}} — Project description
  • {{DATE}} — Current date (YYYY-MM-DD)
  • {{YEAR}} — Current year
  • {{CATEGORY}} — Project category

See references/project-types.md for type-specific variations.

6. Confirm Completion

Report to user:

  • Full path created
  • Files generated
  • Suggested next steps

Project Types

TypeAdditional StructureUse When
generalBase structure onlyDefault, documentation
code-python+ src/, tests/, pyproject.tomlPython projects
code-node+ src/, package.jsonNode.js projects
3d-print+ models/, images/3D printing projects
research+ data/, notebooks/Research/data projects

See references/project-types.md for complete details.

Template Assets

FileSource
README.mdassets/README.template.md
CHANGELOG.mdassets/CHANGELOG.template.md
LICENSE (MIT)assets/LICENSE-MIT.txt
LICENSE (Apache)assets/LICENSE-Apache2.txt
.gitignoreassets/gitignore-general.txt
CONTEXT.mdassets/CONTEXT.template.md
TODO.mdassets/TODO.template.md
DECISIONS.mdassets/DECISIONS.template.md

Integration with wrap-session

This skill creates the structure that /wrap-session writes to:

Init CreatesWrap-Session Updates
README.md (template)README.md (with progress)
CHANGELOG.md ([Unreleased])CHANGELOG.md (with changes)
CONTEXT.md (initial state)CONTEXT.md (current state)
TODO.md (empty)TODO.md (with tasks)
SESSION-LOG/ (empty)SESSION-LOG/*.md

Comments

Markdown supported