agentsclimarketplace

Critical journey document

Skill yarlson/yarstack/plugins/yarstack/skills/critical-journey-document

Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.

Install
npx -y skills add yarlson/yarstack --skill critical-journey-document

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.

SKILL.md

1.9 KB, as published. Nobody here has run it

Critical Journey Documentation

Create one canonical journey record in the repository's established product-documentation location.

Workflow

  1. Confirm what makes the journey critical, its actor, goal, trigger, scope, owner, risk, and canonical document location.
  2. Inspect existing requirements, code, contracts, tests, telemetry, and documentation; reuse repository identifiers and terminology.
  3. Split multiple actors or goals into separate records only when independently useful.
  4. Document the ordered journey, decisions, state changes, success, meaningful failures, recovery, ownership, and evidence links.
  5. Add acceptance, telemetry, blueprint, portfolio, coverage, or story-map sections only when a named consumer or delivery gate requires them.
  6. Record unresolved facts only when the task permits them and names the decision owner and resolution condition.
  7. Use english-text-review on the completed record and apply material findings without changing agreed contracts, identifiers, or domain terms.

Acceptance sections describe product acceptance; test-design owns executable tests. Telemetry sections record agreed contracts rather than inventing events. repo-context-document owns implemented-system flows under docs/context/; rollout-readiness-review owns deployment readiness; spec-update owns semantic decisions.

Do not create a parallel canonical document, mandatory identifier system, speculative telemetry, or an artifact suite by default.

Finish when the record has evidence links, named ownership, explicit unknowns, and only sections with current consumers.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.