chordlens-plan

Plan and validate ChordLens architecture with planner and critic workflows.

Updated Apr 6, 2026

Search Tags:#workflow #planning #architecture #orchestration #phases #critique #peer-review

Ready to run

npx skills add https://github.com/xmun74/chordlens --skill chordlens-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chordlens-plan
Source: https://github.com/xmun74/chordlens/tree/main/.claude/skills/chordlens-plan
Command: npx skills add https://github.com/xmun74/chordlens --skill chordlens-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines pre-implementation planning for ChordLens by defining architecture, file inventories, and interface contracts, reducing ambiguity and rework.

Core Features & Use Cases

Phase-driven planning with planner and plan-critic roles.
Outputs include structured plan documents and critique reports for early validation.
Can be invoked independently via /chordlens-plan or by orchestrator phase 2.

Quick Start

Run the chordlens-plan workflow to generate the initial _workspace plan and a critique, then export the results for Phase 2 orchestration.

Frequently Asked Questions about chordlens-plan

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

FAQPage Schema

How do I plan and validate software architecture before implementation?▼

Architecture planning and validation requires defining file inventories, interface contracts, and structured plan documents, then running an independent critique workflow to reduce ambiguity and rework before execution begins.

How does a planner and critic workflow improve pre-implementation design?▼

A planner and critic workflow separates architecture generation from evaluation, producing structured plan documents alongside critique reports to catch design flaws early and validate deliverables before any code is written.

What's the best way to structure phased design tasks for file inventories and interface definitions?▼

Phased design tasks should define phase 1 deliverables as file inventories, interface definitions, and architecture plans, using structured prompts and deterministic orchestration to satisfy planning and evaluation requirements.

Can I generate a workspace plan and critique report independently without an orchestrator?▼

Yes, you can invoke the planning workflow independently to generate an initial workspace plan and critique report, then export the results for downstream phase 2 orchestration and execution.

Do I need structured prompts and defined workspace artifacts for architecture planning?▼

Structured prompts and clearly defined workspace artifacts are required, as the autonomous planner and critic workflow depends on deterministic inputs to produce validated architecture plans and critique reports.

Why does pre-implementation architecture planning reduce rework in software engineering?▼

Pre-implementation architecture planning reduces rework by defining interface contracts and file inventories upfront, then validating them through independent peer-review critique before execution, eliminating downstream ambiguity.