使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/drewbarontini/equilio-coding --skill equilio-frame開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Frame
Turn an initial signal into an issue-ready account of the problem. Establish what already exists: a request, issue, local file, prototype, or code. Match the depth to the work's impact and uncertainty.
Investigate who is affected, what is happening, evidence, desired outcome, constraints, proposed solutions, and open questions. Test whether a proposed solution addresses the underlying problem before treating it as settled. Distinguish observations from assumptions and decisions.
Write a local Markdown draft the user can inspect. Keep it readable as an emerging issue, not a questionnaire with empty sections. If the project already has an issue, revise the draft against that issue and preserve its useful history and links. When framing is ready, use the project's chosen GitHub, Linear, or local Markdown issue; establish the destination before creating or changing a remote issue. Bring consequential framing to the user for review when appropriate, without making every small edit a gate.
Leave a clear problem, desired outcome, known evidence, current direction if any, and the questions that could alter it. Carry accepted conclusions into the shared issue in prose rather than copying the whole draft. If work stays local, the Markdown issue itself can be the shared account. Never imply a solution or shipment is validated before it is.
