reynldi

reynldi/skills

Command

Three-axis review (Spec / Standards / Risk) of the diff between HEAD and a fixed point, via parallel subagents.

reynldi/skills

Command

Run the full feature delivery pipeline — Planning → Implement → Review → QA — with approval gates; resumes from existing artifacts.

reynldi/skills

Command

Explain a topic like the reader is five years old, using simple English.

reynldi/skills

Command

Stage 7 of /development-workflow — holistic review of the whole feature diff against Product/Technical/Contract Specs.

reynldi/skills

Command

Global multi-agent orchestrator — advisor (second opinion), committee (two contrasting agents plan), handoff (transfer a task), or loop (worker/verifier until done).

reynldi/skills

Command

Adopt a job-role persona — Compass (PM), Forge (backend), Prism (frontend), Gauntlet (QA), Bastion (security), Atlas (DevOps) — with its principles and a thinking level (L1 pragmatic → L4 perfection at scale).

reynldi/skills

Command

Stage 3 of /development-workflow — contract-spec.md (REST/gRPC/Event contracts) from a Technical Spec.

reynldi/skills

Command

Stage 6 of /development-workflow — execute approved tasks.md with tests, per-task reviewer PASS, and checkpoint gates.

reynldi/skills

Command

Stage 1 of /development-workflow — UX-centric Product Spec from a feature idea, user problem, or goal.

reynldi/skills

Command

Stage 5 of /development-workflow — final planning gate; generates tasks.md only when no Blocking/High issues remain.

reynldi/skills

Command

Stage 2 of /development-workflow — implementation-ready Technical Spec from a Product Spec.

reynldi/skills

Command

Stage 4 of /development-workflow — skeptical review of Product/Technical/Contract Specs with severity-ranked findings.

reynldi/skills

Command

Stage P2 of /product-workflow (optional) — research for one decision: use the products of competitors, read their reviews, read why deals were won or lost, find what comes next.

reynldi/skills

Command

Stage P1 of /product-workflow — talk to users, write what they said, and map their problems to possible solutions.

reynldi/skills

Command

Stages P6 and P7 of /product-workflow — set the main number, the weekly numbers, the early signal, and the things that must not become worse. Then record the real numbers after launch.

reynldi/skills

Command

Skeptical review of one PRD before publish or build — find the gaps and the parts that do not belong, then close each one by asking the user question by question.

reynldi/skills

Command

Stage P5 of /product-workflow — write the PRD: introduction with 5W1H, success metrics, user stories, and a requirements table with acceptance criteria. Then give it to /development-workflow.

reynldi/skills

Command

Stage P4 of /product-workflow — score the problems or the possible solutions, give a source for each number, and make a Now / Next / Later roadmap with no dates.

reynldi/skills

Command

Publish the PRD from the current session to Confluence — quality gate against the PRD template, Q&A for the space and parent page with remembered defaults, PIC mentions on open questions and assumptions, then create the page.

reynldi/skills

Command

Stage P3 of /product-workflow — list the assumptions, find the one that can stop the idea, and test it against a number that you write before the test.

reynldi/skills

Command

Run the product loop — learn the problem, research, test the risks, select what to build, write the PRD, set the numbers, build, measure, then start again. Simple English, for all persons.

reynldi/skills

Command

Stage 8 of /development-workflow — QA acceptance testing of the implemented feature against the Product Spec.

reynldi/skills

Command

Quiz the user on a topic (or on this session's unresolved topics) at eli5, medium, or comprehensive level.

reynldi/skills

Command

Run a feature retrospective — review lessons one by one and, with permission, write each into the right spec, skill, constitution, or memory file.