2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| ask | Decision-tree questioning until no doubt remains. Check wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-ask answered questions. Every option must state its impact scope. After each answer, save the record back to the wiki. Use whenever a jsc skill needs user input; skip recording when no {owner}/{repo} is known. |
ask — decision-tree questioning
Every jsc skill that needs user input MUST follow the rules in this skill.
Before asking
- Confirm the repository name
{owner}/{repo}of the current work. Without one, skip steps 2 and 3: ask directly but do NOT record. - Compute
HASH:printf '%s' "{owner}/{repo}" | sha1sum | cut -c1-8 | tr a-f A-F. - Read
QUESTION_CONTENTSandQUESTION_{HASH}viajsc-gitea:wiki. Never re-ask a question already answered in the record; use the recorded answer directly.
Questioning rules
- Present questions as decision-tree options (AskUserQuestion or an equivalent menu), one decision point at a time.
- One question carries one concept; no compound questions. Ask the most important decision first — you may only get one round of answers.
- Every option MUST state its impact scope (what happens if chosen; which files or flows it affects). Add one "why this matters" line to any question that is easy to misread.
- Let each answer decide the next question. Continue until no doubt remains; keep asking while anything is undecided.
- Ask only what the user alone can answer. Look up answers available in code, config files, or environment variables yourself.
After asking
- Without a repository name, do not record; stop here.
- After each Q&A round, apply
templates/question-record.mdto create or updateQUESTION_{HASH}(append new entries; never overwrite old records). - Apply
templates/question-contents.mdto create or updateQUESTION_CONTENTS(add the repository row if missing; otherwise refresh its last-updated time). - The wiki writes above MUST run as a sub agent; the main agent only confirms the write succeeded.