PDIR Development Method

A structured development methodology plugin for Claude Code that implements the PDIR approach: Planejar (Plan), Dividir (Divide), Implementar (Implement), Revisar (Review). This plugin helps manage plugin marketplace development with proper versioning and workflow practices.

What This Plugin Does

This plugin provides guidelines and workflows for developing plugins in the Masterclaude marketplace for Claude Code. It enforces semantic versioning, proper file updates, and clean development workflows to ensure consistent and maintainable plugin development.

Instructions for AI Agent

When this plugin is active, follow these development guidelines:

1. Version Control with Semantic Versioning

Apply semver principles (MAJOR.MINOR.PATCH) to all version updates:

2. Files That Must Be Updated

When making changes to plugins, always update these files in order:

1. **Plugin manifest**: `plugins/<plugin-name>/.claude-plugin/plugin.json`

- Update the `version` field whenever you modify the plugin

2. **Marketplace metadata**: `.claude-plugin/marketplace.json`

- Update the `metadata.version` field when publishing changes

- This should happen after plugin version is updated

3. Standard Development Workflow

Follow this sequence for every development task:

1. **Plan**: Understand the requirement and identify which files need changes

2. **Divide**: Break the task into discrete steps (version updates, code changes, testing)

3. **Implement**: Make the actual code changes

- First: Modify plugin code

- Second: Update plugin version in `plugin.json`

- Third: Update marketplace version in `marketplace.json`

4. **Review**: Verify all version numbers are consistent and changes are complete

5. **Commit**: Create a commit with clear message and push

4. Command Execution Guidelines

When writing or suggesting commands in plugin development:

**Example - BAD**:

```

!test -f file.json && cat file.json || echo "not found"

```

**Example - GOOD**:

```

Check if file.json exists. If it does, read its contents. If not, inform that it's not found.

```

5. When Making Plugin Changes

Always follow this checklist:

6. Version Consistency Rules

Example Usage

**User**: "Add a new feature to the masterclaude plugin that shows plugin statistics"

**AI Response**:

```

I'll implement this new feature using the PDIR method:

**Plan**: This is a new feature (MINOR version bump). Need to:

**Divide**:

1. Implement statistics feature

2. Increment MINOR version in plugin.json (e.g., 1.2.0 → 1.3.0)

3. Update marketplace.json version to match

4. Test and commit

**Implement**: [proceeds with changes]

**Review**: Checking version consistency and testing feature...

```

Notes