๐ Continuous refinement (Idea and Specifications)
๐ Language pair / Par de idioma
Section titled โ๐ Language pair / Par de idiomaโ- English: 11-continuous-refinement.md
- Espaรฑol: ../es/11-refinamiento-continuo.md
๐ฃ๏ธ Friendly prompt (copy/paste)
Section titled โ๐ฃ๏ธ Friendly prompt (copy/paste)โUse this when you are not technical and want the AI to do setup + guidance end-to-end:
Using https://github.com/juanklagos/spec-driven-development-template, create everything needed to carry out my project end-to-end.My project is: [describe your project in plain language].
If my project is new, initialize it with this template and GitHub Spec Kit.If my project already exists, adapt it to idea/specs/bitacora without breaking current behavior.Guide me step by step for my level (beginner/intermediate/advanced), using simple language.Do not skip specification, plan, tasks, refinement trace, logbook, and validation.[!TIP] For startup instructions and prompts, use:
This guide explains how to update project documentation when ideas, priorities, or requirements change.
๐ฏ Goal
Section titled โ๐ฏ GoalโKeep consistency between:
idea/IDEA_GENERAL.mdspecs/(all specifications)bitacora/(real execution records)
๐ Main rule
Section titled โ๐ Main ruleโEvery relevant change must be reflected in 3 places:
- Affected idea or specification.
- Specification history file.
- Session logbook.
๐งญ Change type and required action
Section titled โ๐งญ Change type and required actionโ| Change type | Required action | Where to register |
|---|---|---|
| Product vision change | Update general idea | idea/IDEA_GENERAL.md + bitacora/global/PROJECT_LOG.md |
| New requirement | Create/update specification | specs/NNN-.../spec.md + specs/NNN-.../history.md |
| Technical implementation change | Update plan and tasks | plan.md, tasks.md, history.md |
| Findings-based adjustment | Update research | research.md, history.md, daily log |
| Scope change | Mark impact and priority | specs/INDEX.md + history.md |
๐ Refinement visual flow
Section titled โ๐ Refinement visual flowโflowchart LR A["Change detected"] --> B["Classify change type"] B --> C["Update Idea or Spec"] C --> D["Register in history.md"] D --> E["Update logbook"] E --> F["Revalidate plan and tasks"]โ Quick refinement checklist
Section titled โโ Quick refinement checklistโ- Does this change affect project idea?
- Was active specification updated?
- Was a
history.mdentry added? - Was logbook updated?
- Were tasks reviewed for consistency?
๐ Suggested history.md format
Section titled โ๐ Suggested history.md formatโ| Date | Change type | Summary | Impacted files | Owner |
|---|---|---|---|---|
| 2026-03-12 | Scope change | Split spec into two phases | spec.md, tasks.md |
AI |
๐ค Rule for Artificial Intelligence tools
Section titled โ๐ค Rule for Artificial Intelligence toolsโIf you detect contradiction between idea and specification:
- Do not implement immediately.
- Propose refinement.
- Update documentation.
- Continue implementation only after alignment.
๐ก Quick tips
Section titled โ๐ก Quick tipsโ- Start from a simple one-paragraph project description.
- Ask the AI to confirm the active spec before coding.
- Close every session with validation and a clear next step.
๐ Visual flow
Section titled โ๐ Visual flowโflowchart LR A["Project idea"] --> B["Spec approved"] B --> C["Plan aligned"] C --> D["Tasks prioritized"] D --> E["Implementation"] E --> F["Validation + Logbook"]