design-plan

Generate structured design plans and implementation roadmaps for greenfield pull requests.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/houfu/lq-maintainer-agent --skill design-plan-houfu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-plan
Source: https://github.com/houfu/lq-maintainer-agent/tree/main/skills/design-plan
Command: npx skills add https://github.com/houfu/lq-maintainer-agent --skill design-plan-houfu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing large, complex greenfield feature contributions that are too substantial for standard code reviews, preventing them from stalling in the PR queue.

Core Features & Use Cases

  • Design Path Routing: Automatically identifies category-1 contributions and routes them to a structured design process rather than a code review.
  • Decision Inventory: Generates a clear, ratifiable list of open decisions, separating settled canon from residual questions.
  • Atomic Decomposition: Breaks down large feature requests into an ordered sequence of small, reviewable, and implementable changes.
  • Use Case: When a contributor submits a massive PR for a new subsystem, this skill generates a design plan, drafts necessary ADRs, and decomposes the work into manageable tasks for the maintainer to approve.

Quick Start

Invoke the design-plan skill by running the command lq-maintainer:design-plan pr followed by the pull request number.

Frequently Asked Questions about design-plan

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

FAQPage Schema
How do I break down large pull requests for new features into reviewable tasks?

To break down large greenfield pull requests, you can use architectural decomposition to split massive feature contributions into an ordered sequence of small, reviewable, and implementable changes. This prevents substantial new subsystems from stalling in the PR queue.

What is architectural design planning for greenfield software contributions?

Architectural design planning for greenfield contributions is a structured process that routes substantial new capability additions away from standard code review to generate structured design artifacts and implementation roadmaps aligned with project canon.

Do I need GitHub CLI tools to generate an implementation roadmap from an issue?

Yes, you need GitHub CLI tools to generate an implementation roadmap, as the process requires integration with GitHub CLI tools and internal project documentation to operate on pull requests and issues.

How do I inventory open architectural decisions for a new subsystem?

You inventory open architectural decisions by generating a ratifiable list that separates settled project canon and ADRs from residual questions, ensuring alignment before implementation begins.

When should I route a pull request to a design process instead of a code review?

You should route a pull request to a design process instead of a code review when it is classified as a category-1 new capability addition that is too substantial for standard code review.

Can I draft Architecture Decision Records for a massive feature pull request?

Yes, you can draft necessary ADRs for a massive feature pull request by generating a design plan that separates settled canon from residual questions and creates an implementation roadmap.