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.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "idea" with this command: npx skills add studykit/skillsmp-studykit-studykit-idea

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

General

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

-0studykit

Coding

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

-0studykit

Coding

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

-0studykit

General

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

-0studykit