How do I install the Software Engineering skill?

Run npx skillmds@latest add samraddhashrivastavatech/software-engineering in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Software Engineering safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Software Engineering?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Software Engineering free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Software Engineering?

SAMRADDHASHRIVASTAVATECH (@samraddhashrivastavatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Software Engineering by samraddhashrivastavatech

Name: Software Engineering
Rating: 4.2 (5 reviews)
Author: SAMRADDHASHRIVASTAVATECH

Software Engineering

Orchestrates a one-person software team workflow from request to verified delivery. Use when the user asks to build, maintain, debug, or ship any application, library, API, CLI, desktop, or service — and before writing code.

File contents

Software engineering (one-person team)

Operate as a professional engineer, not a snippet generator.

Always

Read mcp-routing mentally: reuse specialist MCPs.
Call se_detect_environment and se_ecosystem (or se_route) before scaffolding.
If a project path exists, se_discover_project before inventing a new stack.
Produce a short plan (se_plan or equivalent) the user can see.
Implement the smallest thing that satisfies the requirement.
Build and test on the detected toolchain. If a tool is missing, say so (DEPENDENCY_MISSING) — do not pretend.
se_security_audit (and specialist audits) before calling it done.
Document how to run it.

Decision tree

Is it Android / APK / Compose / ADB?
  → android-development-mcp (+ this skill for general process)

Office document (docx/xlsx/pptx)?
  → office-documents-mcp

SQL database work?
  → database-sql-mcp

Windows printers/services/drivers?
  → windows-system-mcp

ASCII tree / folder layout / SDLC blueprint?
  → skill `structure-and-sdlc` + `se_ascii_tree` / `se_sdlc`

Otherwise software (cli, lib, api, web, desktop, native)?
  → software-engineering-mcp templates + this skill

"Build this application" procedure

Requirements — skill requirements-analysis. Extract actors, must-haves, out-of-scope, constraints (OS, offline, license).
Research / tech selection — skill technology-selection. Prefer boring, installed toolchains.
Architecture — skill architecture. Modules, data, APIs, failure modes.
Implement — skill implementation. Match existing project style.
Test — skill testing. At least one automated test that would fail if the feature broke.
Debug — skill debugging if red.
Secure — skill security.
Package / release — skill release-engineering.
Verify — run the happy path; record commands that worked.

Anti-patterns

Defaulting every web app to MERN.
Generating Android apps with se_create_project (wrong MCP).
Unbounded shell.
Silent skip of tests because "the code looks fine".
Duplicating SQL/Office/Windows/Android tools here.

Next files

---name: software-engineeringdescription: Orchestrates a one-person software team workflow from request to verified delivery. Use when the user asks to build, maintain, debug, or ship any application, library, API, CLI, desktop, or service — and before writing code.---# Software engineering (one-person team)Operate as a professional engineer, not a snippet generator.## Always1. Read `mcp-routing` mentally: **reuse specialist MCPs**.2. Call `se_detect_environment` and `se_ecosystem` (or `se_route`) before scaffolding.3. If a project path exists, `se_discover_project` before inventing a new stack.4. Produce a short plan (`se_plan` or equivalent) the user can see.5. Implement the smallest thing that satisfies the requirement.6. Build and test on the **detected** toolchain. If a tool is missing, say so (`DEPENDENCY_MISSING`) — do not pretend.7. `se_security_audit` (and specialist audits) before calling it done.8. Document how to run it.## Decision tree```Is it Android / APK / Compose / ADB? → android-development-mcp (+ this skill for general process)Office document (docx/xlsx/pptx)? → office-documents-mcpSQL database work? → database-sql-mcpWindows printers/services/drivers? → windows-system-mcpASCII tree / folder layout / SDLC blueprint? → skill `structure-and-sdlc` + `se_ascii_tree` / `se_sdlc`Otherwise software (cli, lib, api, web, desktop, native)? → software-engineering-mcp templates + this skill```## "Build this application" procedure1. **Requirements** — skill `requirements-analysis`. Extract actors, must-haves, out-of-scope, constraints (OS, offline, license).2. **Research / tech selection** — skill `technology-selection`. Prefer boring, installed toolchains.3. **Architecture** — skill `architecture`. Modules, data, APIs, failure modes.4. **Implement** — skill `implementation`. Match existing project style.5. **Test** — skill `testing`. At least one automated test that would fail if the feature broke.6. **Debug** — skill `debugging` if red.7. **Secure** — skill `security`.8. **Package / release** — skill `release-engineering`.9. **Verify** — run the happy path; record commands that worked.## Anti-patterns- Defaulting every web app to MERN.- Generating Android apps with `se_create_project` (wrong MCP).- Unbounded shell.- Silent skip of tests because "the code looks fine".- Duplicating SQL/Office/Windows/Android tools here.## Next files- [../mcp-routing/SKILL.md](../mcp-routing/SKILL.md)- [../technology-selection/SKILL.md](../technology-selection/SKILL.md)

Frequently asked questions