Skip to content

aiops: prompt-engineering - Tailor legacy prompts to the book website #449

Open

Description

@ashleyshaw

Current evidence and branch handoff — 25 October 2026

Recorded status: In Progress; implementation presence is not whole-child acceptance. This refresh supersedes stale Backlog/unmodified-prompt assumptions without removing the attached 84-file report or existing acceptance criteria.

Current prompts/ contains 85 tracked files. The catalogue and many retained prompts have changed since the original review. prompts/README.md records 45 rewritten entry points, 20 historical compatibility notices, 19 held originals and one unchanged governance continuation. Treat these as catalogue dispositions and delivered text to verify, not independent proof that every file or underlying audit is accepted. Do not redo changed prompts from the old report blindly.

Refresh the attached report against current files, check retained links/orchestrators and assess unresolved social-account and outside-folder references. Preserve meaningful history, held originals and the separate governance continuation. Editing a prompt does not authorise executing it.

File and branch decision

No fresh rewrite/deletion manifest or exact implementation branch is proposed by this refresh. Preserve the new catalogue and compatibility notices. Produce only an exact residual file-level preview after comparing current content with the attachment and acceptance criteria. Do not repeat the stale two-file candidate plan or infer deletion approval from a disposition label. Scope remains prompts/ only; relocation, guideline/application changes and outside-folder repairs require separate approval. The locally authorised aiops/ classification does not resolve the recorded local/shared PR-template routing conflict; template and exact branch remain unresolved pending residual scope.

Repository evidence: lightspeedwp/ThisOneTimeOnAcidCom at develop revision f99275b085cffd209b9bd42f6e463c0af643099a. Read AGENTS.md and the repository's own branch-validation instructions before separately authorised implementation; repository instructions take precedence. Refresh the base and overlapping changes before choosing a branch. No existing branch is approved for reuse.

The native parent is a coordination record, not an implementation or closing target. No parent reference in future branch names, PR association fields or closing directives. No closing target is established; verify child acceptance, issue mapping and association effects separately. This description update changes no status, hierarchy, native PR association, repository file, branch, settings or approval boundary. Existing GitHub issue sync may propagate this text externally.

Requested outcome

Clean obsolete makeup-portfolio assumptions from prompts/, adapting retained prompts to thisonetimeonacid.com’s book-first purpose. Delete only individually approved irrelevant files.

Context and sources

Review the prompt folder using the attached Markdown report, covering all 84 files at revision 6b3b76baa955acdfaee0d5e4aef39e099b4b083e.

thisonetimeonacid-prompts-review-2026-10-24.md

Coordinate with existing prompt-organisation work and guideline adaptation, without duplicating their scope.

Current prompt and baseline

The review found conflicting portfolio instructions, unsafe cleanup assumptions, broken orchestrators, obsolete paths and commands, and overlapping workflows. The literal ashshaw.makeup match is an Instagram handle requiring a deliberate decision—not automatic domain replacement.

No runtime tests or prompt execution were performed.

Inputs, outputs and constraints

Use the repository instructions, book brief, current routes and attached per-file manifest. Limit implementation to prompts/.

Preserve relevant memoir history and manuscript content. Exclude application changes, prompt relocation, guideline refactoring, protected configuration and automatic task/report deletion.

Proposed approach

Approve each file’s disposition, rewrite retained instructions, consolidate overlapping workflows and repair affected indexes and orchestrators. Reconcile incoming references before approving deletions.

Evaluation and safeguards

Check retained paths, links, commands and workflow consistency against current repository configuration. Review remaining legacy references contextually. Record checks not performed; do not treat historical completion claims as current results.

Acceptance criteria

  • The prompt preserves the agreed intent and defines inputs, outputs, constraints and failure behaviour.
  • Material changes are supported by evidence or explicitly identified assumptions.
  • Validation findings and runtime-test limitations are recorded without invented results.
  • Publication or application receives separate approval.
  • Every original file has a recorded final disposition.
  • Retained prompts support the book-first project; justified historical references are documented.
  • Retained internal links and orchestrator references resolve.
  • No unrelated or protected files are changed.
  • The Markdown review report is attached as issue context.

Next action and missing information

Approve the issue and report attachment, then agree the exact implementation and deletion plan. Social-account relevance and outside-folder reference handling remain unresolved.

Definition of Ready

  • Outcome and scope are sufficiently clear.
  • Required source access and evaluation permissions are identified.
  • Missing information and approval boundaries are explicit.

Definition of Done

  • The proposed prompt and material changes are documented.
  • Agreed checks are completed or explicitly marked not tested.
  • Remaining risks and the approval/handoff decision are recorded.

Branch instructions

Use lightspeedwp/ThisOneTimeOnAcidCom, based on refreshed develop. Exact branch remains unresolved pending approved file-level scope. aiops/ is authorised locally; local and shared pull request template routing disagree and need resolution before implementation. Do not reuse the guideline-refactoring branch or introduce closing associations automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

Medium

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions