All authors
Claude Skills by feiyanglyy-stack
github.com/feiyanglyy-stack12 skills0 installs0 views
- CoverageThe main agent's coverage stage, after the dig lanes. The program lists the planned materials no lane touched, grouped by category and directory, and accounts by itself for the reports and prompts the workbench already cites. Account for every listed group honestly, as not needed or as read in part on purpose and why, or send a follow-up lane to read it, then check again. A group that holds what nothing carries is never accounted for as a group. Send the open candidates and unplaced items wit...Votes: 0GitHub stars: 2
- Cross CheckThe main agent's cross-check stage in a Deepen or Follow up round. Adopt a lane's conclusion only after checking it against the original, the ledger or the code. Settle the suspect links. Give every breakpoint candidate a result, but never light one. Place every work item, decision and design where the project's records place it. Give every item of an earlier generation its destination. Write the rules the Owner's words lane reported, and the adoption record.Votes: 0GitHub stars: 2
- Deepen DispatchThe main agent's dig stage in a Deepen round, and in a Follow up that needs digging. Send lanes by question, all in one pk_send_lanes call, one per plan or stage and one per topic, so that together they answer the four kinds of question. Give every breakpoint candidate to the lane whose plan or topic covers it, listed by id in its brief, one result each. Give the owner's lines, the flagged designs and the generations' destinations each to a lane. History is looked up per question, never read ...Votes: 0GitHub stars: 2
- Lane Follow UpA follow-up lane, sent by the main agent from the coverage check for planned materials no lane touched, and for breakpoint candidates and unplaced items no dig lane settled. Read in full the materials your brief names, and only those, and answer the round's questions they bear on. Give each candidate in your brief one result, either linked or looked for with where. Place what you write from the project's own records. Say exactly what you could not read and why. The program records what you re...Votes: 0GitHub stars: 2
- Lane PlanA deepening lane for one plan or stage, sent by the main agent in a Deepen or Follow up round. For each piece of work that plan names, answer whether it is done, where the evidence is, and what is not wrapped up. Give each breakpoint candidate in your brief one result - link the step you found (pk_link_process), or record where you looked (pk_record_looked). Place every work item in its plan and module from the project's own records. A claim that something is absent names the later tickets yo...Votes: 0GitHub stars: 2
- Lane SlotA skeleton lane, sent by the main agent in a First usable round (or in a Follow up whose document chain changed) to fill one group of workbench slots from the document chain. Copy what the documents state with pk_fill_from_table and pk_fill_from_headings before judging, then judge the rest - placement from the project's own records, one Design per Spec section, each earlier generation's items and where each went, each owner's line it is given. Write your slots with sources and hand back a com...Votes: 0GitHub stars: 2
- Lane TopicA deepening lane for one topic or kind of question, sent by the main agent in a Deepen or Follow up round. Topics include the owner's meaning, the document chain and decisions, the code as it stands, or a theme orientation saw. Answer the brief's questions across the whole history, looking history up per question in the ledger rather than reading version by version. Judge each finding by the uniform verdict, give each breakpoint candidate one result, place each decision on what it acts on, gi...Votes: 0GitHub stars: 2
- OrientationThe main agent's first stage in every round of the clerk method (First usable, Deepen, Follow up). Learn the project's shape from the ledger and the current top documents. Write the layer map, the rules the documents state and the organizing plan. Accept or reject the candidate generations. Map the document chain onto the workbench's slots, then write the round's questions and one seven-part brief per lane. Use it at the start of a round, and again after a restart when pk_round_state says the...Votes: 0GitHub stars: 2
- ReconcileThe main agent's reconcile stage after the skeleton lanes, in a First usable round and in a Follow up whose document chain changed. Join the lanes' slots into one trunk. Place every work item in its plan and module, and every decision on the module or plan it acts on, from the project's own records. Settle the candidate generations and record where each generation's items went. Write as rules the owner's lines the Owner's words lane reported. Write only what was found; draw no conclusion that...Votes: 0GitHub stars: 2
- Skeleton DispatchThe main agent's skeleton stage in a First usable round, and in a Follow up whose document chain changed. Send the skeleton lanes, one per group of workbench slots and grouped by the project's document chain, all in one pk_send_lanes call. Each lane copies what the documents state with the fill tools and writes its slots with sources. One lane holds the owner's lines. Once every lane has come back, read the reports and move on to reconcile.Votes: 0GitHub stars: 2
- Spot CheckThe independent spot-check of a Deepen or Follow up round, its final re-check, sent by the program after the synthesis. Check every breakpoint candidate a lane looked for and did not find, every "missing" conclusion, every reason that left an item unplaced, and in full what the synthesis wrote and every note current now. Sample the rest. Light a candidate only once it holds. Correct what is wrong in place, and record every check, a Wrong one as timing or substance.Votes: 0GitHub stars: 2
- SynthesisThe round's product look-back, in a session of its own after the main agent's handover. Read the handover and every lane report first. Then answer the round's questions for the owner, judge the six things, write notes, send-backs and area understanding, give each note standing from an earlier round one result, and write the round's Result. In a First usable round, write only what was found.Votes: 0GitHub stars: 2