all publishers

forsonny

@forsonny source repo

40 published skills

  1. ▌
    Deep Discovery 2 · forsonny bundle
    Use when the user asks for deep discovery, 100-question brainstorming, idea interrogation, architecture stress testing, strategy vetting, weakness finding, hole-poking, exhaustive exploration, planning or auditing Codex plugins or skills, or pre-commitment review of a design, plan, strategy, architecture, product, business idea, trading system, or problem space.
    3 repo stars
  2. ▌
    Plan Novel 2 · forsonny
    Create or substantially revise the novel premise, structure, chapter plan, character arcs, and required world foundations.
    3 repo stars
  3. ▌
    Write Chapter 2 · forsonny
    Draft the next chapter or a specified chapter while preserving continuity and established voice.
    3 repo stars
  4. ▌
    Revise Chapter 2 · forsonny
    Substantively revise a specified chapter for structure, prose, character, pacing, or continuity.
    3 repo stars
  5. ▌
    Continuity Pass 2 · forsonny
    Audit a chapter range or manuscript scope for contradictions and continuity risks.
    3 repo stars
  6. ▌
    Finalize Manuscript 2 · forsonny
    Review a substantially complete manuscript and produce or execute a prioritized revision plan.
    3 repo stars
  7. ▌
    Judging · forsonny
    Dispatch the Court on evidence-only inputs (contract + diff + verify output + confidence). The Court is not a persona; it is a structured adjudicator.
    3 repo stars
  8. ▌
    Planning · forsonny
    Decompose a confirmed contract into an atomic task DAG with wave ordering. Every task cites one or more contract criterion ids.
    3 repo stars
  9. ▌
    Executing · forsonny
    Dispatch one fresh subagent per plan task inside a per-task git worktree. Capture diff and tool output; never carry state across dispatches.
    3 repo stars
  10. ▌
    Resetting · forsonny
    On verify or judge fail, append a non-null lesson to the Ledger and re-queue the task. Null lessons are refused; the task escalates instead.
    3 repo stars
  11. ▌
    Verifying · forsonny
    Run the four verification probes (Exists, Substantive, Wired, Functional) per criterion. All four green per criterion or the criterion fails.
    3 repo stars
  12. ▌
    Contracting · forsonny
    Author a machine-readable contract before execution. Produces anvil/contract.yml with four verification-level slots per criterion and Ledger-sourced counter-examples.
    3 repo stars
  13. ▌
    Using Anvil · forsonny
    Bootstrap loader for the DG-Anvil plugin. Enumerates the five primitives, seven skills, five commands, and the core loop. Loaded at session-start.
    3 repo stars
  14. ▌
    Authoring Skills · forsonny
    Meta-skill governing every change to any skill file. Requires a RED-then-GREEN subagent pressure transcript before a skill change is accepted.
    3 repo stars
  15. ▌
    Plan Novel · forsonny
    Create or substantially revise a novel premise, structure, chapter plan, character arcs, and required world foundations. Use for a new novel or major structural replan.
    3 repo stars
  16. ▌
    Write Chapter · forsonny
    Draft the next chapter or a specified chapter from the accepted outline while preserving manuscript continuity, character knowledge, and established voice.
    3 repo stars
  17. ▌
    Revise Chapter · forsonny
    Substantively revise a specified chapter for structure, prose, character, pacing, or continuity while preserving its intended story function and established voice.
    3 repo stars
  18. ▌
    Continuity Pass · forsonny
    Audit a chapter range or current manuscript for contradictions, timeline errors, knowledge leaks, rule violations, and unresolved continuity risks.
    3 repo stars
  19. ▌
    Finalize Manuscript · forsonny
    Review a substantially complete manuscript for structural gaps, continuity problems, unresolved promises, chapter order, and revision priorities before final polish.
    3 repo stars
  20. ▌
    Brainstorming · forsonny bundle
    Use when the human partner asks to build, add, change, or modify anything (features, components, functionality, behavior). Explores intent, requirements, and design before implementation. Hard-gated; nothing implements until the human partner approves the written product spec.
    3 repo stars
  21. ▌
    Using Leyline · forsonny bundle
    Use when starting any conversation - establishes how to find and use Leyline skills, requiring a Skill check before any response including clarifying questions.
    3 repo stars
  22. ▌
    Writing Plans · forsonny bundle
    Use when you have approved specs and a clean worktree with a green baseline, before any code is written. Decomposes the specs into 2-5 minute tasks with exact file paths, complete code, and verification. Runs inside the worktree from stage 3; hands off to subagent-driven-development or executing-plans.
    3 repo stars
  23. ▌
    Deep Discovery · forsonny bundle
    Use after the product spec is approved, before any implementation work. Pressure-tests the spec with a 100-question self-interrogation where each question builds on the previous answer. Returns critical issues, strengths, and a revised proposal. Material revisions loop back to brainstorming.
    3 repo stars
  24. ▌
    Writing Skills · forsonny bundle
    Use when authoring a new skill for the Leyline plugin, modifying an existing skill's behavior-shaping text, or adding to the testing-anti-patterns / forbidden-phrases lists. Applies TDD-for-prose - baseline pressure test without the skill, write the minimal skill text that rebuts the observed rationalizations, verify compliance, refactor against new loopholes.
    3 repo stars
  25. ▌
    Executing Plans · forsonny
    Use when a committed plan exists, the harness does NOT support subagent dispatch, and the implementation is ready to begin. Executes the plan inline with human-partner checkpoints, task-by-task. Fallback to subagent-driven-development; hands off to stage 7 review on completion.
    3 repo stars
  26. ▌
    Using Git Worktrees · forsonny
    Use when starting feature work that needs isolation from the current workspace, or before executing implementation plans. Creates an isolated git worktree with systematic directory selection and a green-baseline test gate. Runs after Interrogate, before Plan.
    3 repo stars
  27. ▌
    Design Brainstorming · forsonny bundle
    Use when the approved product spec touches any user-facing surface, before any implementation skill runs on that surface. Explores flows, states, accessibility, and voice. Hard-gated; nothing implements until the human partner approves the written UX spec.
    3 repo stars
  28. ▌
    Design Interrogation · forsonny bundle
    Use at stage 2 after the UX spec has been approved and deep-discovery has cleared the product spec, when scope warrants dedicated UX pressure-testing. Runs a 100-question interrogation targeted at flows, state completeness, accessibility, voice, and platform appropriateness. Material revisions loop back to design-brainstorming.
    3 repo stars
  29. ▌
    Systematic Debugging · forsonny
    Use when any bug, test failure, or unexpected behavior surfaces, before proposing or applying any fix. Enforces four sequential phases (root cause investigation, pattern analysis, hypothesis formation, verification) and blocks fix proposals until root cause is identified. An overlay during stage 5.
    3 repo stars
  30. ▌
    Receiving Code Review · forsonny
    Use when receiving code review feedback, before implementing any suggestion. Drives the READ -> UNDERSTAND -> VERIFY -> EVALUATE -> RESPOND -> IMPLEMENT response pattern one finding at a time. Blocks performative agreement and blind implementation.
    3 repo stars
  31. ▌
    Requesting Code Review · forsonny
    Use at stage 7 after all tasks complete and before merging, to verify the entire feature meets requirements. Dispatches the code-reviewer subagent with branch-level constructed context (SHAs, plan excerpt, product spec reference, review log). Per-task quality review is a separate Stage 5 path via code-quality-reviewer-prompt.md; do not invoke this skill per-task.
    3 repo stars
  32. ▌
    Receiving Design Review · forsonny
    Use when receiving design review feedback, before implementing any UX or accessibility suggestion. Drives the same READ -> UNDERSTAND -> VERIFY -> EVALUATE -> RESPOND -> IMPLEMENT pattern as receiving-code-review, with additional forbidden phrases that block UX-specific performative agreement and taste-based dismissal.
    3 repo stars
  33. ▌
    Test Driven Development · forsonny bundle
    Use when implementing any feature, bug fix, refactor, or behavior change, before any production code is written. Enforces RED-GREEN-REFACTOR. The failing test is written first, observed failing for the right reason, then the minimal code that passes is written. An overlay on every stage-5 code task.
    3 repo stars
  34. ▌
    Requesting Design Review · forsonny
    Use when completing any task or feature that touches a user-facing surface, before merging a branch with UX changes. Dispatches the design-reviewer subagent in parallel with requesting-code-review, with constructed context (UX spec path, surfaces touched, accessibility evidence, SHAs).
    3 repo stars
  35. ▌
    Design Driven Development · forsonny
    Use when implementing any task whose "Files:" block touches a user-facing surface, before writing the code for that surface. Enforces the DRAW-BUILD-RECONCILE cycle: the UX artifact is the source of truth, the implementation instantiates it, and any divergence is resolved explicitly. An overlay during stage 5 alongside test-driven-development.
    3 repo stars
  36. ▌
    Accessibility Verification · forsonny
    Use whenever you are about to claim a user-facing surface is complete - before committing, before marking the task done, before any success claim. Requires running an accessibility check fresh in the current message and reading its output before any completion claim. An overlay during stage 5 alongside verification-before-completion.
    3 repo stars
  37. ▌
    Dispatching Parallel Agents · forsonny
    Use during stage 5 execution when two or more genuinely independent problems surface at the same time, each understandable without context from the others. Dispatches one fresh subagent per problem concurrently. Not a pipeline stage; a tactical skill called from within subagent-driven-development.
    3 repo stars
  38. ▌
    Subagent Driven Development · forsonny bundle
    Use when a committed plan exists in the worktree, the harness supports subagent dispatch, and the implementation is ready to begin. Dispatches a fresh subagent per task (implementer, spec reviewer, code-quality reviewer, plus design reviewer when surfaces are touched). Hands off to stage 7 review on completion.
    3 repo stars
  39. ▌
    Finishing A Development Branch · forsonny
    Use when implementation is complete, Stage 7 reviews are cleared, and the branch is ready to integrate. Verifies tests fresh, determines base branch, presents four options (merge local / push and PR / keep / discard), executes the chosen path, and cleans up the worktree. Pipeline terminates here.
    3 repo stars
  40. ▌
    Verification Before Completion · forsonny
    Use whenever you are about to claim that work is complete, fixed, or passing - before committing, creating a PR, or reporting status. Requires running the verification command fresh in the current message and reading its output before any claim is made. An overlay during stage 5 and every handoff in the pipeline.
    3 repo stars