consolidate

Files (18)

• LICENSE
• SKILL.md
• openai.yaml · agents/
• delivery-slice-template.md · assets/
• functionality-template.md · assets/
• technical-spec-template.md · assets/
• artifact-links.md · references/
• catalogue.md · references/
• context.md · references/
• decisions.md · references/
• delivery-slice-example.md · references/
• delivery-slices.md · references/
• functionality-example.md · references/
• local-document-delivery.md · references/
• proposals.md · references/
• reconciliation.md · references/
• record-format.md · references/
• technical-work.md · references/

SKILL.md (first lines)

# Consolidate

Maintain product intent, behavior, authority, and evidence for owners and agents
across sessions. Adapt representation, hierarchy, workflow, and depth to the product;
cover its relevant contract. Apply [artifact links](references/artifact-links.md)
whenever citing documents or tickets.

## Resolve authority and intent

Resolve [project configuration](../setup-beto-frega-skills/references/project-configuration.md#resolve-configuration),
including external files. Read canonical destinations, native representation,
conventions, governing decisions, maintenance sources, affected records, and existing
authorization. Preserve identifiers and settled choices.

Setup owns configuration. For an unresolved destination or convention, name the gap
and suggest `$setup-beto-frega-skills`. Continue the work you have authority for, and
write clearly labeled drafts where a write is blocked. Canonical records keep
precedence over drafts, and an unavailable configured destination stays a named gap.

Read only relevant routes; combine them when needed:

| Route | Read when |
| --- | --- |
| [Catalogue](references/catalogue.md) | Finding or maintaining functionalities, audiences, jobs, behavior, value, and cost. |
| [Delivery slices](references/delivery-slices.md) | Recording selected increments, acceptance, dependencies, exposure, coverage, or delivery evidence. |
| [Context](references/context.md) | Maintaining direction, business context, shared rules, vocabulary links, or discovery evidence. |
| [Decisions](references/decisions.md) | Recording product/business choices, rationale, history, or their contract consequences. |
| [Proposals](references/proposals.md) | Shaping an investment proposal or pitch. |
| [Technical work](references/technical-work.md) | Preserving technical choices or preparing a scoped tracker spec. |
| [Reconciliation](references/reconciliation.md) | Maintaining implementation, deployment, release, exposure, or flags; investigating drift. |

Use [write-adr](../write-adr/SKILL.md) for architecture and the
[glossary format](../domain-modeling/CONTEXT-FORMAT.md) for definitions under configured
domain conventions. Feature behavior belongs in the catalogue; cross-functional
rules have shared authority. Link derived specs and tickets to those records.

Consolidate known knowledge; grill only consequential gaps blocking this update.
Interview handoffs retain selected increments, confirmed product/technical choices,
references, and deferred questions. Feature knowledge and ideas may exceed selected
delivery scope.

## Write the affected knowledge

Read [record format](references/record-format.md) before writing living records;
it owns consolidation, native history, bounded changelogs, template, and example.

Keep approval, proposals, observations, and assumptions apart. Approval comes from
the conversation or project evidence; code and flag configuration alone do not show it. Preserve
unknowns and discrepancies; actual-state claims carry source, time, scope, and coverage.

Use configured objects, properties, sections, and relationships. Keep one authority
per meaning; cover known behavior, exceptions, and implementation/verification
scenarios. Scale detail and governance to the product, but cover every rule. Update
linked records affected by accepted changes. Label interaction illustrations
replaceable and state binding outcomes explicitly.

Act within existing authorization. Release, flag operations, schedules, and new
policy need their own authorization. Read reconciliation
before an authorized flag operation.

## Verify completion

Apply [local document delivery](references/local-document-delivery.md) for local edits.
Read back saved records and relationships: verify identity, representation, content,
authority/timing, source coverage, decision/shared-rule/work/evidence links, and the
whole-document record-format checks. Account for every affected record with a
verified result or named gap.

For lookups/reviews, return canonical links and findings. For changes, report saved,
proposed, unknown, and unverifiable effects separately. Report drafts, acceptance,
implementation, and verified release as separate outcomes.

From BetoFrega/skills, MIT.

More from BetoFrega/skills