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:

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:

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-opus-4.5/
        ├── 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

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

Template Assets

Integration with wrap-session

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