Install
$ agentstack add skill-anton-g-kulikov-metacoding-metacoding-workflow ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Metacoding Workflow
Use this skill when the user wants disciplined execution rather than ad hoc coding.
Start Here
- Read
references/project-context.mdfirst. - Read
references/workflow-rules.mdfor the operating contract. - Read
references/repository-organization.mdbefore planning or editing. - Read
references/platform-adaptation.mdif the repo lacks task docs, test docs, or git context. - Load only the language reference that matches the task:
references/typescript.mdreferences/javascript.mdreferences/node.mdreferences/react.mdreferences/python.md
Core Rules
- Ground in the repo before asking clarifying questions.
- Capture scope, success criteria, and constraints before changing code.
- Enforce mandatory TDD: document test intent, write or identify failing tests first, then implement production code.
- Work one bounded task at a time.
- Verify changes with tests and direct checks.
- Maintain MECE documentation: update the correct artifact without duplicating the same concept across multiple docs.
- Close with a commit-ready handoff, an actual VCS action, or an explicit completion confirmation.
Enforcement
- Do not skip directly to coding when repo inspection can reduce uncertainty.
- Do not bypass TDD unless the user explicitly accepts the exception and the reason is recorded.
- Do not switch to unrelated work mid-task. Queue it for later.
- If a new blocker is required to finish the active task, treat it as a subtask.
- If git actions are unavailable or out of scope, stop at a clean handoff instead of forcing a commit.
- If repo artifacts are missing, bootstrap them from
assets/templates/before implementation or explicitly propose them. - Keep repository organization and documentation structure aligned with
references/repository-organization.md.
Bundled Templates
Use these templates when the repo does not already provide an equivalent artifact:
assets/templates/task-entry.mdassets/templates/test-plan.mdassets/templates/repeated-task-checklist.mdassets/templates/changelog-entry.md
Keep the workflow strict, but adapt the exact artifact shape to the repository you are working in.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: anton-g-kulikov
- Source: anton-g-kulikov/metacoding
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.