Introduce PromptyDumpty

[dasiths]

Description

This PR introduces PromptyDumpty package support for HVE Core, making it easy to install chatmodes, prompts, instructions, and scripts into any project using a simple package manager.

Key Changes:

• Added dumpty.package.yaml manifest file defining all HVE Core artifacts
• Organized 14 chatmodes, 10 prompts, 17 instructions, and 20 script files into 8 categories
• Updated README.md with PromptyDumpty installation instructions
• Leverages new PromptyDumpty v0.8.0 support for chatmodes and instructions artifact types

Installation:

pip install prompty-dumpty
dumpty install https://github.com/dasiths/hve-core

Users can now selectively install components by category (ado, git, development, documentation, testing, security, linting, data-science) or install everything at once.

Related Issue(s)

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with prompt-builder chatmode and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot chatmode (.github/chatmodes/*.chatmode.md)

Other:

• Other (please describe): Package manager integration (PromptyDumpty)

Testing

Validation:

• Manifest validated with dumpty validate-manifest dumpty.package.yaml
• All 61 artifacts correctly categorized (14 chatmodes, 10 prompts, 17 instructions, 20 files)
• Verified PromptyDumpty v0.8.0 supports new chatmodes and instructions types

Expected Installation Structure:

.github/
├── chatmodes/hve-core/     # 14 chatmode files
├── prompts/hve-core/       # 10 prompt files
├── instructions/hve-core/  # 17 instruction files
└── files/hve-core/scripts/ # 20 script files

Package Categories:

• ado - Azure DevOps workflows (5 agents, 4 prompts, 5 instructions)
• git - Git workflows (2 agents, 6 prompts, 2 instructions)
• development - Development tools (8 agents, 2 prompts, 9 instructions, 2 scripts)
• documentation - Documentation generators (3 agents, 1 instruction)
• testing - Testing tools (1 agent, 1 instruction)
• security - Security validation (1 agent, 3 scripts)
• linting - Code quality tools (13 script files)
• data-science - Data science workflows (3 agents)

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)

AI Artifact Contributions

• Used prompt-builder chatmode to review contribution
• Addressed all feedback from prompt-builder review
• Verified contribution follows common standards and type-specific requirements

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege

Additional Notes

Benefits of PromptyDumpty Integration:

• Easy Distribution: Users can install HVE Core components with a single command
• Selective Installation: Choose only the categories needed for specific workflows
• Version Control: Lock to specific versions via Git tags
• Workspace Integration: Automatically configures VS Code settings for Copilot

Future Enhancements:

• Create versioned releases with Git tags (e.g., v1.0.0)
• Add more granular categories if needed
• Consider publishing example packages for specific use cases

[Copilot]

Pull request overview

This PR introduces PromptyDumpty package manager support for HVE Core, enabling users to install chatmodes, prompts, instructions, and scripts via a simple command-line tool rather than manually cloning the repository. The implementation adds a comprehensive package manifest that catalogs all 61 artifacts across 8 functional categories, and updates the README with installation instructions highlighting this as the recommended approach.

Key Changes:

• Added dumpty.package.yaml manifest defining package metadata and all HVE Core artifacts
• Updated README.md to feature PromptyDumpty installation as Option 1 (recommended)
• Organized artifacts into 8 categories enabling selective installation by workflow type

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
dumpty.package.yaml	New package manifest cataloging 14 chatmodes, 10 prompts, 17 instructions, and 20 script files with metadata, file paths, and category assignments
README.md	Added PromptyDumpty installation instructions as recommended Option 1, with pip install command and documentation link

[Copilot]

The copilot-instructions entry is missing the categories field, which all other instructions have. Since this is a comprehensive root-level instruction file that should apply to all development contexts, consider adding categories: [development] or document in the manifest comments why this instruction is category-free.

Suggested change

	installed_path: copilot-instructions.md
	installed_path: copilot-instructions.md
	categories: [development]

[Copilot]

The PromptyDumpty documentation URL https://dumpty.dev should be verified. If this URL doesn't exist or is a placeholder, consider linking to the actual PromptyDumpty documentation (e.g., GitHub repository or PyPI page).

[Copilot]

[nitpick] Consider adding a brief note about where PromptyDumpty installs the artifacts (e.g., .github/chatmodes/hve-core/, .github/prompts/hve-core/, etc.) and whether any workspace configuration is needed after installation, to help users understand the difference between Option 1 and Option 2.

[martinpeck]

The tool itself looks interesting. My question is "how do we want/expect hve-core to be installed by users?".

The current guidance (and, I assume, testing) assumes that hve-core is cloned beside the project you're working on. That has some benefits:

• the hve-core files do not pollute the project
• the hve-core files can easily be updated if improvements are made (by git pull)

However, the current guidance also has downsides:

• if the user modifies the hve-core files for their own purposes, those look like changes in git

The PromptyDumpty approach is different. Instead of using git it grabs copies of the files needed. It also adds these files into the project repo.

Personally, I like the PromptyDumpty approach. It's much clearer that these hve-core files become the users's files, and there there is no expectation that these files will be updated with back-compat in mind. Project-specific changes to these files can be committed along with the project.

However, I worry that having 2 very different approaches confuses the user. Which do they pick, and why? My suggestion is that hve-core has one "opinionated" view of how it is used, and how it is installed, and that it should avoid having multiple options. If PromptyDumpty is that approach then great.

If you want to have two approaches then both need to be tested, and both need to be explained in a way that helps users know which to choose and why.

[BTW, I have no skin in this game at all. I just want to make sure that hve-core doesn't scare first-time users off by presenting a matrix of options and approaches, or give itself problems in terms of testing/supporting/documenting the differences in those approaches]

[dasiths]

Thanks for having a look Martin.

Personally, I like the PromptyDumpty approach. It's much clearer that these hve-core files become the users's files, and there there is no expectation that these files will be updated with back-compat in mind. Project-specific changes to these files can be committed along with the project.

This is the idea. You can customize the prompts to work within your environment. Dumpty allows you to update the prompts from source again but these updates will get captured as changes in your own git repo.

The PromptyDumpty approach is different. Instead of using git it grabs copies of the files needed. It also adds these files into the project repo.

Yes the assets are considered yours once they get pulled down. It actually uses git under the hood but that is opaque. Once the assets are copied over, the link is severed. Those assets become the repos files from that point onwards. Dumpty lockfile just tracks all of it to make future removal or updates easier.

If you want to have two approaches then both need to be tested, and both need to be explained in a way that helps users know which to choose and why.

100%

[WilliamBerryiii]

@dasiths can you file an issue where we can talk through this proposal (rather than in the context of the PR)?

[dasiths]

@dasiths can you file an issue where we can talk through this proposal (rather than in the context of the PR)?

Created #112