Add PitchDocs plugin to Plugins & Extensions

[nathanschram]

Adds PitchDocs to the Plugins & Extensions section — a documentation generation plugin that produces marketing-ready README, CHANGELOG, CONTRIBUTING, AI context files, and 15+ more files with evidence-based feature extraction and quality scoring.\n\n100% Markdown, zero runtime dependencies, MIT licensed. Install via /plugin marketplace add littlebearapps/lba-plugins.

[qodo-code-review]

Review Summary by Qodo

Add PitchDocs documentation generation plugin

✨ Enhancement 📝 Documentation

Walkthroughs

Description

• Adds PitchDocs plugin to Plugins & Extensions section
• Provides documentation generation with marketing-ready outputs
• Includes feature extraction, quality scoring, GEO optimization

Diagram

flowchart LR
  A["Plugins & Extensions<br/>README.md"] -- "adds PitchDocs<br/>entry" --> B["Documentation<br/>Generation Plugin"]
  B -- "produces" --> C["README, CHANGELOG,<br/>CONTRIBUTING, etc."]
  C -- "with" --> D["Feature Extraction<br/>& Quality Scoring"]

Loading

File Changes

1. README.md 📝 Documentation +1/-0

Add PitchDocs plugin documentation entry

• Adds PitchDocs plugin entry to Plugins & Extensions section
• Includes link to GitHub repository and installation instructions
• Describes key features: marketing-ready documentation generation, feature extraction, quality
 scoring, GEO optimization
• Specifies installation command via marketplace

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Unclear install syntax 🐞 Bug ✓ Correctness

Description

README’s “How to use” section documents installs as /plugin install /, but the new PitchDocs entry
uses /plugin install pitchdocs@lba-plugins. If the @marketplace form is unsupported (or just
undocumented here), users will be blocked or confused by conflicting instructions.

Code

README.md[21]

+- [PitchDocs](https://github.com/littlebearapps/pitchdocs) - Documentation generation plugin that produces marketing-ready README, CHANGELOG, CONTRIBUTING, AI context files, and 15+ more files with evidence-based feature extraction, quality scoring, and GEO optimisation; install with `/plugin marketplace add littlebearapps/lba-plugins` then `/plugin install pitchdocs@lba-plugins`.

Evidence

The README defines only one install form (/plugin install /). The new entry introduces a different
syntax without any explanation or other examples, making the README self-contradictory.

README.md[5-14]
README.md[21-21]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README currently documents plugin installation as `/plugin install <owner>/<repo>`, but the new PitchDocs entry uses `/plugin install pitchdocs@lba-plugins`. This makes the README inconsistent and may mislead users.
### Issue Context
If the `@marketplace` syntax is correct, the README should explicitly document it alongside the existing install form. If it’s not correct, the PitchDocs entry should be changed to match the documented install format.
### Fix Focus Areas
- README.md[5-14]
- README.md[21-21]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Overlong description ☑ 🐞 Bug ⛯ Reliability

Description

The PitchDocs description is much longer and more marketing-like than the repo’s contribution
guidelines suggest, reducing scanability. Consider shortening it to a concise summary and moving
detailed claims to the linked repo.

Code

README.md[21]

+- [PitchDocs](https://github.com/littlebearapps/pitchdocs) - Documentation generation plugin that produces marketing-ready README, CHANGELOG, CONTRIBUTING, AI context files, and 15+ more files with evidence-based feature extraction, quality scoring, and GEO optimisation; install with `/plugin marketplace add littlebearapps/lba-plugins` then `/plugin install pitchdocs@lba-plugins`.

Evidence

The repository contribution guidelines explicitly request short, simple descriptions; the PitchDocs
line is lengthy and feature-dense compared to the intended list style.

contributing.md[7-10]
README.md[21-21]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PitchDocs entry is very long relative to the repo’s guideline to keep descriptions short and simple.
### Issue Context
The list is meant to be scannable; detailed feature breakdowns can live in the linked project.
### Fix Focus Areas
- README.md[21-21]
- contributing.md[7-10]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-code-review]

1. Unclear install syntax 🐞 Bug ✓ Correctness

README’s “How to use” section documents installs as /plugin install <owner>/<repo>, but the new
PitchDocs entry uses /plugin install pitchdocs@lba-plugins. If the @marketplace form is
unsupported (or just undocumented here), users will be blocked or confused by conflicting
instructions.

Agent Prompt

### Issue description
The README currently documents plugin installation as `/plugin install <owner>/<repo>`, but the new PitchDocs entry uses `/plugin install pitchdocs@lba-plugins`. This makes the README inconsistent and may mislead users.

### Issue Context
If the `@marketplace` syntax is correct, the README should explicitly document it alongside the existing install form. If it’s not correct, the PitchDocs entry should be changed to match the documented install format.

### Fix Focus Areas
- README.md[5-14]
- README.md[21-21]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[nathanschram]

Addressed both Qodo review items:

1. Shortened description — trimmed to a concise one-liner matching the style of other entries in the repo.

2. Simplified install — changed from the two-step marketplace add + plugin install to a single-step /plugin marketplace add littlebearapps/lba-plugins, consistent with the repo's conventions.