How do I install the Aidlc Feature skill?

Run npx skillmds@latest add aws-samples/aidlc-feature 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.

What does the Aidlc Feature skill do?

Run the AI-DLC workflow with the feature scope baked in — no scope detection. Default for new features, practical depth. Packaging over `/aidlc --scope feature`, which works without this skill. It is listed under Productivity on SkillMD.

Is Aidlc Feature safe to use?

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

Which AI agents work with Aidlc Feature?

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 Aidlc Feature free to use?

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

Who published Aidlc Feature?

aws-samples (@aws-samples) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidlc Feature by aws-samples — Agent Skill

Name: Aidlc Feature
Author: aws-samples

File contents

AI-DLC — feature scope

Drive the AI-DLC engine with the feature scope fixed. This is the same deterministic forwarding loop the /aidlc orchestrator runs, with --scope feature baked into the first next so scope detection is skipped. The engine owns all routing; the conductor persona arrives on the first directive's conductor_persona field — adopt it for the whole run.

The loop

directive = bun .kiro/tools/aidlc-orchestrate.ts next --scope feature $ARGUMENTS
Act on directive.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see aidlc-common/protocols/stage-protocol.md.
bun .kiro/tools/aidlc-orchestrate.ts report --stage <directive.stage> --result <outcome> [--user-input "<text>"] when the directive names a stage; omit --stage only for non-stage report round-trips.
Repeat from step 1 until directive.kind == done.

Pass $ARGUMENTS through verbatim after --scope feature; the engine parses any flags (--status, --stage, --test-run, …) and the --scope from the state file always wins on an existing workflow, so re-running a started workflow resumes it. To run a different scope, use /aidlc --scope <other> instead.

Frequently asked questions

Aidlc Feature