Execute software feature stories sequentially from planning artifacts and update execution logs.
npx skills add https://github.com/MmtBkn/swe --skill swe-exec
Please help me install this Agent Skill. Skill: swe-exec Source: https://github.com/MmtBkn/swe/tree/main/swe-exec Command: npx skills add https://github.com/MmtBkn/swe --skill swe-exec
This Skill automates the process of turning planning artifacts like stories, epics, and PRDs into working code, ensuring features are built and validated systematically.
.next.md) and marks completed artifacts..swe/stories/user-auth/ sequentially, updating the execution log and marking each story as done upon completion.Use the swe-exec skill to implement the stories in the directory .swe/stories/user-auth/.
High-intent search queries and answers about installing and using this skill.
Automating feature development from planning artifacts involves sequentially processing stories, epics, and specs to generate working code. This process rebuilds project context from input paths to ensure informed implementation and systematic progression throughout the development workflow.
Sequential story implementation executes stories in a defined order to ensure logical progression. It processes planning artifacts sequentially, maintains an execution log in `.next.md`, and updates artifact statuses to mark completed stories as done upon successful implementation.
The best way to track progress during feature implementation is by maintaining an execution log. This approach updates a `.next.md` file and marks completed artifacts, ensuring systematic validation and clear visibility into the progression of implemented user stories.
Yes, workflow automation requires strict adherence to input path conventions for proposals, tech specs, epics, and stories. These specific directory structures are necessary to ensure accurate context rebuilding and correct implementation within the `.swe` ecosystem.
Yes, contextual execution rebuilds and utilizes project context from proposals, tech specs, and epics. This ensures informed implementation by accurately reconstructing the necessary background information before executing and implementing software features from planning artifacts.
Code execution requires input path conventions within the `.swe` ecosystem to ensure accurate context rebuilding. Adhering to these specific directory structures for proposals, specs, epics, and stories guarantees that the implementation process has the correct background information.
Paxeer-NetworkManages project artifacts via basicmemory tools with enforced YAML frontmatter and ProjectId tracking.
reez455GAutomate CI/CD pipelines with GitHub Actions for quality checks, testing, and deployment.
adolfoaranaes12Break down epics into user stories with acceptance criteria and sprint groupings.
morodomiGenerate failing tests and coordinate parallel workers for TDD RED phases.