complainProject

Converts user complaints into a change request and PRD updates.

Updated May 21, 2026
One-click install
npx skills add https://github.com/kinetas/harness_engineering --skill complainproject
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complainProject
Source: https://github.com/kinetas/harness_engineering/tree/main/complainProject
Command: npx skills add https://github.com/kinetas/harness_engineering --skill complainproject

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams capture vague frustrations and improvement ideas, then converts them into a structured change request and a PRD update that can be executed.

Core Features & Use Cases

  • Guided complaint intake: Asks one question at a time to collect problems, proposed changes, technical adjustments, constraints, and priorities.
  • Change Request document generation: Writes doc/CHANGE_REQUEST.md with a clear summary, problems list, requested changes, out-of-scope items, and an ordered priority list.
  • PRD synchronization: Updates doc/PRD.md by modifying only the affected sections while preserving the overall PRD structure.

Quick Start

Run /complainProject and answer the guided questions to produce doc/CHANGE_REQUEST.md and update doc/PRD.md.

Frequently Asked Questions about complainProject

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert user complaints into structured PRD updates?

To convert user complaints into structured PRD updates, you can use an interactive Q&A process that gathers frustrations one at a time, generates a change request document, and modifies only the impacted PRD sections with updated timestamps.

What is the best way to document change requests during product iteration?

The best way to document change requests during product iteration is by generating a markdown file that captures problem summaries, requested changes, out-of-scope items, and an ordered priority list alongside the existing PRD.

Can I update specific sections of a PRD without altering the entire document structure?

Yes, you can update specific sections of a PRD without altering the entire document structure by synchronizing only the impacted sections based on the collected change requirements, preserving the overall layout while adding updated timestamps.

How does guided requirements gathering work for project maintenance?

Guided requirements gathering for project maintenance works by asking one question at a time to collect problems, proposed changes, technical adjustments, constraints, and priorities, transforming vague feedback into actionable documentation.

Do I need existing workspace files to generate a change request document?

Yes, you need existing workspace files to generate a change request document, specifically requiring a PRD markdown file and a company state JSON file to check current project parameters before writing the update.

Why does priority planning matter when processing user feedback into PRDs?

Priority planning matters when processing user feedback into PRDs because it ensures the generated change request includes an ordered priority list, allowing teams to systematically execute technical adjustments and address the most critical constraints first.