🧭 Advanced guide (high-consistency teams)

🌍 Language pair / Par de idioma

• English: 15-advanced-guide.md
• Español: ../es/15-guia-avanzada.md

🗣️ Friendly prompt (copy/paste)

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].
Guide me step by step for my level and do not skip specification, plan, tasks, logbook, and validation.

Who is this for:

• Teams standardizing SDD across multiple AI tools and contributors.

Goal

Deliver equivalent outcomes regardless of agent/model, with governance and quality gates.

Advanced operating model

1. Canonical AI instructions:

• template-context/core-instructions/AGENT_OPERATING_SYSTEM.md

2. Spec Kit-first workflow:

• /speckit.constitution
• /speckit.specify
• /speckit.plan
• /speckit.tasks
• /speckit.implement

3. Hard gates:

• approved spec.md
• consistent plan.md
• passing validations

Prompt pack (Advanced)

Prompt A: Multi-agent standard mode

Operate with strict SDD governance and Spec Kit-first flow.
Enforce gate: no code without approved spec and consistent plan.
Use one active spec only.

Prompt B: Refinement protocol

Detect scope/priority/requirement changes.
If detected, stop implementation and update:
- active spec
- history.md
- specs/INDEX.md (if status/priority changed)
- bitacora
Then continue.

Prompt C: Governance closeout

Close this session with:
objective, active spec, changes, validations, risks, exact next step.
Include release/governance impacts if any.

Governance checks

• SemVer release discipline.
• Changelog updated per release.
• No merge when SDD gate fails.

Metrics to track

• % specs with up-to-date history.md
• % sessions with full bitacora
• out-of-scope changes per sprint
• cross-agent consistency rate

Validation

./scripts/validate-sdd.sh . --strict
./scripts/check-sdd-gate.sh .

More prompts

• Prompt matrix
• Validated prompt bank
• Prompts by template feature

Next references

• Quality checklists
• Architecture decisions
• Release checklist

💡 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

flowchart LR
  A["Project idea"] --> B["Spec approved"]
  B --> C["Plan aligned"]
  C --> D["Tasks prioritized"]
  D --> E["Implementation"]
  E --> F["Validation + Logbook"]