Total Skills
16
Author Profile: studykit
Skills published by studykit with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
arch
0
Stars
0
Downloads
0
auto-coding
0
Stars
0
Downloads
0
auto-scaffold
0
Stars
0
Downloads
0
ci-setup
0
Stars
0
Downloads
0
discard
0
Stars
0
Downloads
0
domain
0
Stars
0
Downloads
0
spec
0
Stars
0
Downloads
0
usecase
0
Stars
0
Downloads
0
Published Skills
arch
"This skill should be used when the user needs to design or iterate on system architecture — technology stack, external dependencies, component design, information flows, interface contracts, and test strategy. Common triggers include: 'architecture', 'design the system', 'component design', 'tech stack', 'how should we build this', 'system design', 'interface contracts', 'test strategy', 'what tools should we use'. Writes the result as a4/architecture.md (wiki page) following the spec-as-wiki+issues layout."
Repository SourceNeeds Review
auto-coding
This skill should be used when the user wants to drive the agent-based implement + test loop over the tasks already authored in a4/{task,bug,spike,research}/. Common triggers include: 'auto-coding', 'implement the tasks', 'run the implementation loop', 'kick off the agents', 'coder', 'agent loop'. Two stages: an autonomous loop body (pick → implement → test, up to 3 cycles), then a user-driven post-loop review that classifies failures or confirms UC ship. Works with or without UCs — UC ship-review is conditional on per-task implements: being non-empty.
Repository SourceNeeds Review
auto-scaffold
This skill should be used when the user needs the LLM to perform project scaffolding — directory structure, dependency installation, build configuration, and a minimal running entry point. Common triggers include: 'scaffold the project', 'set up the project', 'bootstrap the project', 'create the dev environment'. Produces repo files only; does not author any wiki page. Test environment setup is owned by /a4:ci-setup, which can be invoked separately at any time.
Repository SourceNeeds Review
ci-setup
This skill should be used when the user needs the LLM to set up or update the CI / test environment — installing test runners (unit + integration), creating runner configuration, writing one minimal passing test per tier, wiring task entry points, and writing a4/ci.md as the test-execution reference. Common triggers include: 'set up testing', 'add integration tests', 'set up CI', 'write ci.md', 'update test environment'. Re-callable any time test infrastructure evolves.
Repository SourceNeeds Review
discard
This skill should be used when the user wants to discard an existing task across any of the four issue families (task / bug / spike / research). Common triggers: 'discard task <id>', 'drop task <id>', 'abandon this task', 'task <id> is no longer needed'. The skill flips the task's `status:` to `discarded` via direct frontmatter edit (the PostToolUse cascade hook refreshes `updated:`) and optionally appends a `## Why Discarded` body note. UC-cascade discards (when a UC flips to `discarded` and the cascade hook auto-discards related tasks) are not in scope — they are handled by the hook automatically. Authoring is the matching `/a4:task`, `/a4:bug`, `/a4:spike`, or `/a4:research` skill.
Repository SourceNeeds Review
domain
"This skill should be used when the user needs to extract or revise the cross-cutting Domain Model — concepts, relationships, state transitions — from an existing use-case set. Common triggers include: 'domain model', 'extract concepts', 'glossary', 'class diagram', 'state diagram', 'concept relationships', 'state transitions', 'domain.md', 'reconcile vocabulary'. Writes a4/domain.md (wiki page) following the spec-as-wiki+issues layout. Authored separately from usecase: usecase captures per-UC actor/situation/flow; domain extracts the cross-cutting vocabulary that emerges across UCs."
Repository SourceNeeds Review
spec
"This skill should be used when the user has converged on the shape of an artifact (format, protocol, schema, renderer rule, CLI surface) and wants to commit it as a prescriptive implementation contract. Writes the spec to `a4/spec/<id>-<slug>.md` with proper frontmatter and body, soft-links any related research tasks (a4/research/<id>-<slug>.md) via standard markdown body links and optional `related:` frontmatter entries, optionally records decision rationale in the `## Decision Log` appendum, and nudges affected wiki pages (architecture / context / domain / actors / nfr). Triggers: 'document this format', 'write up the spec', 'capture this shape', 'this is the spec', 'spec this out', or after the user and LLM converge on a prescriptive shape. Accepts either no argument (extract spec from recent conversation) or a short summary / title (used as a seed). Also handles re-invocation on an existing draft spec to activate it. Requires an `a4/` workspace."
Repository SourceNeeds Review
usecase
This skill should be used when the user has a vague idea for software but doesn't know exactly what to build, when the user says 'help me figure out what to build', 'what should I make', 'shape this idea', 'use cases', 'gather requirements', 'what do users need', 'break this down', or when a rough idea needs to be shaped into concrete Use Cases through a Socratic interview. Writes per-UC issue files plus wiki pages into <project-root>/a4/ following the spec-as-wiki+issues layout.
Repository SourceNeeds Review
brainstorm
This skill should be used when the user wants to brainstorm, generate ideas, explore possibilities, or think through options. Triggers: 'brainstorm', 'generate ideas', 'think of options', 'explore possibilities', 'creative thinking', 'what are some ideas for', 'help me think about'. Assesses the situation and selects the appropriate technique — SCAMPER, Free Brainstorming, Mind Mapping, Reverse Brainstorming, Random Stimulus, and more.
Repository SourceNeeds Review
breakdown
"This skill should be used when the user needs to derive a batch of task files from existing usecase / spec / architecture inputs. Common triggers include: 'breakdown', 'derive tasks', 'task batch', 'batch tasks from spec', 'plan the implementation tasks'. Writes per-task files at a4/task/<id>-<slug>.md only — no wiki page output. Requires (usecase OR spec) AND ci.md to enter; otherwise redirects to /a4:ci-setup, /a4:spec, /a4:usecase, or /a4:task. The agent-driven implement + test loop is in /a4:auto-coding; single ad-hoc tasks come through /a4:task, /a4:bug, /a4:spike, /a4:research."
Repository SourceNeeds Review
bug
This skill should be used when the user wants to log a single bug task — a tracked defect fix against expected behavior. Common triggers: 'log a bug', 'create a bug task', 'open a bug for X', 'track this regression', 'file a bug'. Optional implements: (UC paths the bug traces to) and/or spec: (spec paths whose expected behavior the bug violates); writes a4/bug/<id>-<slug>.md. Single-task entry. For batch UC/spec-driven generation use /a4:breakdown; for the implement loop use /a4:auto-coding; for task/spike/research use the matching skill (/a4:task, /a4:spike, /a4:research); to discard a task use /a4:discard.
Repository SourceNeeds Review
extract-usecase
This skill should be used when the user wants the LLM to extract or batch-shape Use Cases from raw input — an existing codebase, an idea, brainstorm notes, or a file path — without an interactive interview. Triggers: 'extract use cases from code', 'extract use cases', 'auto-generate use cases', 'extract-usecase', 'generate use cases from this idea', 'no interview needed just generate', 'run extract-usecase on'. Writes per-UC files plus context.md / actors.md / nfr.md into <project-root>/a4/. Independent skill — does not assume any other skill ran before or runs after; the user picks the next step.
Repository SourceNeeds Review
idea
This skill should be used when the user explicitly invokes /a4:idea inside a project that uses the a4 plugin's a4/ workflow. Captures a one-line idea as a new issue file at a4/idea/<id>-<slug>.md, or discards an existing one. The skill allocates the next global id, slugifies the provided text, and writes the frontmatter + body so the user only has to type the idea itself.
Repository SourceNeeds Review
research
This skill should be used when the user wants to author a single research task — a time-boxed written investigation of a technical topic or comparison of alternatives. Common triggers: 'research X', 'investigate X', 'compare X vs Y', 'evaluate alternatives for', 'I need a research task on'. Required: mode (comparative | single); options (option names) when comparative. The body itself is the deliverable — sources consulted, findings, options. No production code is produced. Writes a4/research/<id>-<slug>.md. `implements:` / `spec:` / `cycle:` are forbidden on research. For exploratory PoC code rather than written investigation, use /a4:spike instead. To discard a task use /a4:discard.
Repository SourceNeeds Review
spike
This skill should be used when the user wants to author a single spike task — a time-boxed exploration to unblock a decision (XP sense). PoC, investigation, benchmark — throwaway code. Common triggers: 'spike on X', 'add a spike', 'create a spike for', 'I need a quick PoC', 'investigate X technically before deciding', 'time-box an exploration'. Writes a4/spike/<id>-<slug>.md and proposes a project-root artifacts/spike/<id>-<slug>/ artifact directory for the throwaway code. `implements:` / `spec:` / `cycle:` are forbidden on spike. For pure written investigation without throwaway code, use /a4:research instead. Single-task entry. To discard a task use /a4:discard.
Repository SourceNeeds Review
task
This skill should be used when the user wants to author a task — a unit of regular implementation work (new functionality, extension, refactor). Common triggers: 'add a task', 'create a task', 'I need a task for', 'task for <UC>'. Optional implements: (UC paths) and/or spec: (spec paths); writes a4/task/<id>-<slug>.md. For bug/spike/research use the matching skill (/a4:bug, /a4:spike, /a4:research); to discard a task use /a4:discard.
Repository SourceNeeds Review