iterate_plan_nt

Apply user feedback to existing implementation plans without thoughts-locator components.

2|Updated May 8, 2026

Search Tags:#planning #codebase #implementation #plan #iterate #no-thoughts

Ready to run

npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill iterate-plan-nt-brightblock

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iterate_plan_nt
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/iterate_plan_nt
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill iterate-plan-nt-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables updating an existing implementation plan without relying on the thoughts locator or thoughts analyzer agents, streamlining plan maintenance in projects that use a non-standard thoughts setup.

Core Features & Use Cases

No-thoughts plan iteration: updates an existing plan by applying user feedback directly to the plan file.
Safe, surgical edits: preserves plan structure and phase sequencing while adapting scope, success criteria, and milestones.
Use Case: when a project wants to adjust timelines or add a new validation phase without introducing thoughts-locator components.

Quick Start

Provide the plan file path and the requested changes to begin iterating on the plan.

Frequently Asked Questions about iterate_plan_nt

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

FAQPage Schema

How do I update an implementation plan without using the thoughts directory?▼

To update an implementation plan without the thoughts directory, apply user feedback directly to the plan file. This approach enforces surgical edits to scope, phases, and success criteria while preserving the existing plan structure and formatting for projects using a non-standard setup.

When do I need to iterate on a codebase plan without thoughts-locator components?▼

You iterate on a codebase plan without thoughts-locator components when your project uses a non-standard thoughts setup. This is needed to adjust timelines, scope, or add validation phases without introducing standard thoughts-analyzer dependencies into the project.

Can I adjust scope and success criteria in a plan while preserving its structure?▼

Yes, you can adjust scope, success criteria, and milestones while preserving plan structure. The iteration process applies surgical edits that maintain phase sequencing and validates changes against the plan's existing formatting and required fields.

What is the best way to apply user feedback to an existing implementation plan?▼

The best way to apply user feedback to an existing implementation plan is through direct, surgical edits to the plan file. This method updates milestones and phases without relying on thoughts-analyzer components, ensuring formatting and required fields remain validated.

Does plan iteration work for projects that do not use standard thoughts directory components?▼

Yes, plan iteration works for projects without a standard thoughts directory. It updates plans by applying feedback directly, bypassing the need for thoughts-locator or thoughts-analyzer components while enforcing surgical edits and validating formatting.

What are the limitations of iterating on plans without the thoughts-analyzer?▼

A limitation of iterating without the thoughts-analyzer is that you bypass standard thoughts directory integration. The process relies solely on direct plan file edits, enforcing surgical updates and validation against existing formatting without analyzing external thought dependencies.